Cova Promotions V2 Integration with Buddi

Modified on Wed, 14 May at 3:27 PM

Overview

This document explains how Cova's new Promotions V2 feature integrates with Buddi. The primary goal of this integration is to streamline promotion management for retailers by automatically syncing promotions created in Cova directly into the Buddi platform. This eliminates the need to duplicate promotion setup across both systems.
 


How it Works

When a retailer creates a promotion using Cova's Promotions Hub (their V2 system), Buddi will automatically detect and display that promotion to customers.

  • Automatic Sync: Promotions created, updated, or deleted in Cova Promotions Hub will be reflected in Buddi without manual intervention. A promotion may not appear immediately as menus sync at a predetermined time interval (e.g. 15 minutes, etc). You can either force sync your menu or wait until the next sync cycle completes.
     
  • No Duplication: Retailers only need to manage their promotions within the Cova Promotions Hub.
     
  • If a product is discounted with two different promotions we will only display the most recently created promotion.
     

Supported Promotion Types

Initially, Buddi's integration with Cova Promotions V2 supports the most common discount types:

  • Dollar Amount Off ($ Off): e.g., $5 off a specific product or category.
  • Percentage Off (% Off): e.g., 10% off all edibles.


Important: At this time, Bundling (e.g., buy product A + product B for a special price) and BOGO (Buy One, Get One) promotions created in Cova Promotions V2 are not supported and will not appear in Buddi.

 


Important Considerations

  • V1 vs. V2 Exclusivity: Retailers must use either Cova's older Promotions system (V1) or the new Promotions Hub (V2). They cannot use both simultaneously for Buddi integration.

  • Date & Time Restrictions: Buddi fully respects the start and end dates/times set for promotions in Cova.
     
  • Time Zone Conversion: Buddi automatically converts the promotion times from UTC (as provided by Cova) to the retailer's local time zone. This ensures promotions start and end accurately according to the store's operating hours.

  • Day of Week Restrictions: If a promotion in Cova is configured to run only on specific days (e.g., "Weekend Sale" active only Saturday & Sunday), Buddi will enforce this and only show the promotion on those designated days.

  • Promotions Prioritized by Date: If a product is part of two different promotions, the most recently updated promotion will take precedence.

  • Product Sale Prices Take Priority: Individual products where a sale price was applied through the catalog take priority over promotional pricing. 

 


Technical Details (API Information)

For informational purposes, Buddi fetches promotion data from Cova using a specific API endpoint structure.


  • Base URL Structure:

    https://api.covasoft.net/Promotions/v1/Companies/{CompanyID}/ConditionCapabilities/{ConditionBits}/PromotionTypeCapabilities/{PromotionBits}/Promotions

  • {CompanyID}: The unique identifier for the retailer's company in Cova.

  • {ConditionBits} (Static Value: 16496): This tells Cova which promotion conditions Buddi can understand and support. The value 16496 represents a combination of supported conditions like product classifications, catalog IDs, etc. Buddi uses this static value to filter for compatible promotions.

  • {PromotionBits} (Static Value: 1536): This tells Cova which promotion types Buddi supports. The value 1536 represents the combination of "Dollar Off" (512) and "Percentage Off" (1024). Buddi uses this static value to fetch only these specific types of promotions.

  • Example Full URL:

    https://api.covasoft.net/Promotions/v1/Companies/YOUR_COMPANY_ID/ConditionCapabilities/16496/PromotionTypeCapabilities/1536/Promotions


Resources

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article