Batch reports need an intentional relationship to products and lots. We define which system supplies the document, how editors replace a file and what a shopper sees when a report is unavailable. Checkout integrations receive the same attention: an age-check response, payment decision or destination rule must lead to a defined next step. Those requirements come from your approved operating policies. Development translates them into explicit behavior that can be tested, including exceptions that would otherwise leave an order or customer stranded.
A working integration also needs an understandable interface. CBD web design can explain a verification request or document link in the context of the current purchase, using your reviewed wording. CBD website support can then monitor changes in provider behavior and investigate failed callbacks using documented order states. Test cases should include returning customers, interrupted verification and mixed baskets, so the implementation accounts for ordinary complications without implying that a software connection alone establishes the eligibility of every sale.