A broad catalogue.
A clear path to purchase.

Store design extends far beyond promotional banners. Fast selection, readable product details and a clear basket determine usability. B2B journeys add item-code entry, repeat ordering and specification import. Show pack size, minimum quantity and lead time before checkout so orders do not return for avoidable corrections.

During design, document representative screens and expected user actions. For each decision, identify what editors maintain, what comes from another system and who owns its freshness.

Acceptance check: A first-time mobile visitor can find the relevant service and next step.

The workflow connects these stages: Build basket → Check inventory → Validate account terms → Confirm order. Each transition has an owner, inputs and a visible result. Before implementation, map the normal journey, correction, cancellation and repeated actions. Interface status must represent a confirmed state rather than a button click.

Acceptance check: Returns and retries preserve input without duplicating the result.

Products have variants, units, pack multiples and warehouse availability. Orders preserve prices and terms at confirmation time. Displayed stock is separate from a reservation; final checks happen at checkout. If some lines are unavailable, identify them precisely and offer an agreed substitute or split shipment.

Acceptance check: Reference data changes do not overwrite an agreed document.

Buyers work within an organisation and contract. One employee builds a basket, another approves purchasing and accounting staff access documents. Price changes after approval need visible history. Credit terms and limits are supplied by authorised systems or company rules, never trusted from browser input.

Acceptance check: A different organisation cannot retrieve a restricted file by direct URL.

Connect products, prices, inventory and documents to the chosen accounting systems. Define update batches, timing and processing order. Repeated order submissions return the original outcome. An ERP outage must not produce a confirmed order message while reservation and account checks remain pending.

Acceptance check: An unavailable source never appears as a confirmed success.

For long operations, acknowledge receipt and retain the result identifier. Retrying after a connection loss must not create a second record. Separate user-correctable errors from cases requiring a specialist, preserving input under the agreed handling rules. Design empty, loading, forbidden and unavailable states before implementation rather than after launch.

Acceptance check: A repeated event does not apply an operation twice.

Build search structure around categories, brands and useful product selections. Support item codes and agreed synonyms, with alternatives for unavailable products. Keep personalised prices out of public caches. Test rapid basket entry, long product names and realistically large catalogues.

Acceptance check: Search and filters lead to useful pages without endless duplicates.

The first release covers the complete journey from “Build basket” to “Confirm order”, supporting pages and editable fields. Test mobile views, roles, forms, documents and integration failures in staging. Save the previous state and define rollback before switching. Handover includes editor instructions, the exchange design and a checklist for future releases.

Acceptance check: Recovery has been tested on a copy, and editors can maintain fields independently.