Example audience
Merchants deciding between catalogue, quotes and checkout
Merchants deciding between catalogue, quotes and checkout
Consider a merchant deciding whether customers should browse a catalogue, request a reviewed quote or place a paid order. The choice depends on product data, pricing, shipping, tax inputs and how staff fulfill or reject work.
Define products and variants, customer price or quote rules, order state, supported destinations and the authoritative stock/payment records. If Stripe is selected, scope its provider access and test environment, signed-event handling, retries, duplicate protection and reconciliation. A browser return or an architecture diagram alone does not establish successful payment or a production integration.
For a store that needs a catalogue and checkout, see what to agree in an ecommerce development scope. If payment events also need to update another tool, plan API integration for order and payment records.
Describe the workflow, users and decisions you need help assessing. The relevant service page explains the scope to discuss.