Skip to main content

Promotion\/Pricing Imports

Distributor reference for promotion and pricing imports with PromotionEDBL and PromoOverrideEDBL: required fields, how promotions are matched or created, and updating PromotionProducts safely. Requires v23.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 23.01

Pre-Conditions

Minimum Requirements of Report or spreadsheet used to import:
​
​

  • ProductID or ProductIDTranslation
    ​
    ​

  • Amount or Case Amount
    ​
    ​
    ​

Additional Optional Fields:
​
​

  • PromotionID or PromotionIDTranslation to link to an existing promotion, or be able to easily update imported promotions in bulk
    ​
    ​

  • Promotion Type to help dictate what type of promotion should be used
    ​
    ​

  • Market
    ​
    ​

  • Participation
    ​
    ​

  • Min Purchase (Quantity necessary for quantity discount)
    ​
    ​

  • Min Product Count
    ​
    ​

  • Start Date
    ​
    ​

  • End Date
    ​
    ​

  • Salesman Override
    ​
    ​

  • Promotion Name

Steps

System Behavior:

PromotionEDBL

  • Used to import new pricing or update full promotion records
    ​
    ​

  • Will create products that do not already exist in the system if ProductIDTranslation is mapped
    ​
    ​

  • Will create promotions, promotion products, markets, zones, and promotion customers as needed
    ​
    ​

PromoOverrideEDBL
​
​

  • Used to override invoice transactions to a specific promotion
    ​
    ​
    ​

Recommendations:
​
​

  • If using PromotionEDBL to update existing pricing, please include all PromotionProducts of the Promotion. PromotionProducts that are not included will be deleted from the Promotion.
    ​
    ​

  • Break the data down by promotion type and import each promotion type separately.
    ​
    ​

  • If importing new promotions, use PromotionIDTranslation to help easily link on promotions in the system.
    ​
    ​

  • If updating existing promotions, map the PromotionID.
    ​
    ​

  • Import initially using markets and later use a table import to import zones to make it simpler to initially map the import.

Fields And Definitions

PromotionEDBL:

Best Used for:

  • Pricing Imports
    ​
    ​

  • Pricing Updates. Include all PromotionProducts of the Promotion. PromotionProducts that are not included will be deleted from the Promotion
    ​
    ​

Other Promotion EDBL Information

  • The minimum requirement for the Promotions EDBL is a Product column. As long as there is a Product in the source file, the Promotions EDBL can run successfully, and without a Product, the EDBL reports an error.
    ​
    ​

  • When Promotion ID or Promotion ID Translation is mapped, and the EDLB can match an existing Promotion based on it, that Promotion and its related Promotions Products records will get updated.
    ​
    ​

  • When Promotion ID or Promotion ID Translation is not mapped, but PromotionName, Condition, PromotionType, MarketID, StartDate, and EndDate are mapped, those fields will be used to match an existing Promotion ID, and if found, that Promotion and its related Promotions Products records get updated.
    ​
    ​

  • When no existing Promotions record can be match through any of the above conditions, a new Promotions records gets created, and the related tables' records are created or updated accordingly.
    ​
    ​
    ​

InvoicePromoOverrideEDBL:

Best Used for:
​
​

  • Overriding invoice transactions to a specific promotion

Best Practices

Import routines are an incredibly powerful tool and if used incorrectly, can affect alot of data. Test thoroughly on small data sets before importing.

If users are running into setup issues or have questions, reach out to Encompass Support.

If there is a complex process that consists of a report and import routines that the user doesn't want to setup? Contact our professional services to team to assist.

Did this answer your question?