Trigger Logic and Batching

5-Minute Batching

To prevent overwhelming partner endpoints, product changes are batched and dispatched in 5-minute intervals. Payloads will contain a max of 25 updates, if more than 25 updates exist for a company, multiple webhooks will be dispatched.

Note: Do not expect sub-second real-time syncs. Updates are accumulated and sent in bursts.

Mapping Requirements

To ensure data integrity, our pipeline only propagates updates for products that meet specific criteria. You will not receive a webhook if:

• No Barcode: The variant is not mapped to a barcode in the BudSense Product Database (BPD).
• No Company Association: The variant is not present at any of your allowed companies.

Note on Future Updates: Currently, webhooks provide standardized BPD product data. Support for customer-specific data (such as company-specific overrides or variants without barcodes) is under development and will be released in a future update.

Multi-Company Updates

If a single product update affects multiple companies assigned to your account, you will receive a separate webhook request for each company.

We send separate requests because each company may have a different configuration setup within BudSense. This allows your system to process the update correctly within the specific context of that company’s environment.