Context
The repository already reserves /trade/login, /trade/order, and /trade/orders for a future trade experience.
Deep Dive Brewing plans to replace its current brewery management, inventory, and sales system (Ollie) with a separate custom application after the Sea Saba booking platform is complete. Because that future system should ultimately own inventory, sales, order processing, pricing, and related operational data, this website must not independently build a competing source of truth.
Goal
Define the future website-side trade customer portal and its integration boundary with the planned brewery management application.
Potential customer-facing capabilities include:
- authenticated access for approved trade customers
- current product/availability information sourced from the future brewery management system
- wholesale information and account-specific resources
- submitting an order or order request
- viewing prior orders or requests
Scope
This issue is intentionally tabled for later implementation. Before implementation, determine which responsibilities belong in the future brewery management app and which belong in this website.
The website should primarily be the customer-facing surface. Inventory, sales, pricing, fulfillment, and authoritative order state should not be duplicated here if the future brewery application owns them.
Acceptance criteria
Timing
Backlog / tabled. Revisit after the custom brewery management, inventory, and sales application is underway and its APIs/data ownership are known.
Context
The repository already reserves
/trade/login,/trade/order, and/trade/ordersfor a future trade experience.Deep Dive Brewing plans to replace its current brewery management, inventory, and sales system (Ollie) with a separate custom application after the Sea Saba booking platform is complete. Because that future system should ultimately own inventory, sales, order processing, pricing, and related operational data, this website must not independently build a competing source of truth.
Goal
Define the future website-side trade customer portal and its integration boundary with the planned brewery management application.
Potential customer-facing capabilities include:
Scope
This issue is intentionally tabled for later implementation. Before implementation, determine which responsibilities belong in the future brewery management app and which belong in this website.
The website should primarily be the customer-facing surface. Inventory, sales, pricing, fulfillment, and authoritative order state should not be duplicated here if the future brewery application owns them.
Acceptance criteria
Timing
Backlog / tabled. Revisit after the custom brewery management, inventory, and sales application is underway and its APIs/data ownership are known.