Overview
Understanding Bell's Brewery integration
Who this is for: Distributors, retailers and other customers that buy from Bell's Brewery, and the order, shipping and finance teams that support them.
Scope: This guide describes typical practice for this kind of trading relationship; Bell's Brewery's own program details are confirmed during onboarding.
Bell's Brewery is a craft brewer based in Kalamazoo and Comstock, Michigan. Beer moves through the three-tier system: the brewer or importer sells to licensed wholesalers, which sell to retailers, so order, depletion and invoice data has to line up across tiers and state rules.
Distribution through wholesalers in many states with seasonal and limited releases means allocation and depletion reporting matter. In this kind of program the points that usually matter are depletion and inventory reporting from the wholesaler, returnable kegs and pallets, date codes and recalls. Bell's Brewery's own EDI or API specification is not part of this guide and no Bell's Brewery document was read, so treat the document list and workflows below as typical practice for this type of company and confirm the documents, X12 version, delivery method and testing steps with Bell's Brewery before you build.
ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, and then monitors every file after go-live and handles partner changes, as software, as a managed service or both.