Overview
Understanding BrewDog integration
Who this is for: Distributors, retailers and other customers that buy from BrewDog, and the order, shipping and finance teams that support them.
Scope: This guide describes typical practice for this kind of trading relationship; BrewDog's own program details are confirmed during onboarding.
BrewDog is a Scottish craft brewer that also brews in the United States at a brewery in Canal Winchester, Ohio. 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.
US-brewed and imported beers go through wholesalers while bars and its own venues add direct supply, so the order and shipment flows differ by product source. 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. BrewDog's own EDI or API specification is not part of this guide and no BrewDog 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 BrewDog 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.