Choosing an Ecommerce Operating Model Before Writing a Website Brief

An ecommerce website brief should follow the operating model. A store that ships stocked products, takes custom orders, or sells downloads needs different inventory, checkout, fulfilment and support rules. Decide how orders will work before choosing a theme or feature list.

How to make the decision

Write down the product type, who owns stock, where fulfilment happens, payment timing, returns, delivery geography and who handles exceptions. Map one standard order and one difficult order from discovery to support. Then decide which rules the platform must automate and which can remain a manual workflow at launch. Keep the website brief tied to those decisions: catalog structure, account needs, tax display, shipping options, notifications, integrations and reporting. Test the operating model with the people who fulfil and support orders, not only the marketing team.

Worked example

Synthetic UAE merchant sells made-to-order gifts and stocked accessories. The first brief asks for a single generic checkout. A trial order reveals that gifts need an approved design and ten-day lead time while accessories ship tomorrow. The team separates product types, displays lead times before payment, defines when a custom order becomes non-cancellable, and adds a support handoff. The resulting brief has two test orders and a clear exception route rather than a long wishlist of apps.

What to verify

• Is the fulfilment owner named?
• Can a buyer see accurate lead times before paying?
• Have one normal and one exception order been tested?
• Are integrations tied to an actual workflow?

Limits and ownership

Platform documentation can describe available features, but it cannot decide your refund policy, service promise or operational capacity. Have the responsible owner approve these before development.

What to hand over

Hand the development team a decision sheet with the two order journeys, exception owner, approved customer promises and unresolved platform questions. Use it to reject features that do not serve the operating model. When the business later adds a new product type, revisit these rules before changing checkout or fulfilment logic.

Common question

Can we choose the platform first?

You can shortlist platforms, but final selection should follow the model and the processes the team can actually operate.

Next useful step

Use Designing a Store Migration Rehearsal Environment for the adjacent decision. For an implementation review, see Megvi’s ecommerce website development service and bring the source records, proposed checks and open exceptions.

Source checked 28 October 2026: Shopify Help Center: migrating store data and operations. Check current platform settings before changing a live store or report.

The worked example is illustrative and is not presented as a Megvi client outcome.