Before adding an online channel, follow one real order

Pick an order you can reconstruct with the person who handled it. Use an ordinary example rather than your most unusual sale. If the product has sizes or colours, identify the exact variant. “The blue shirt” is less useful than the specific item your customer ordered.

Keep customer names, phone numbers, addresses and payment details out of the working copy. You need the sequence of actions, not a customer's personal information. Give the example a simple reference so everyone follows the same order.

Draw five steps: product selection, availability check, order recording, payment confirmation, and collection or delivery. Under each, note who acts, which record they use and what they change. Add the stock update wherever it actually happens in your process.

Ask where the current product name, variant and price are maintained. Then ask which stock record the team trusts before confirming an order. Is the quantity checked for the whole shop, one location or a particular variant? Write down the answer rather than assuming every number means the same thing.

Payment status deserves its own check. A customer saying they have paid, a payment confirmation and an order being ready to collect are different events. Record how your team distinguishes them and who makes the decision to continue.

Circle any place where someone copies information, checks the same quantity again or asks a colleague for an update. These are useful questions for a walkthrough. They are not proof that every manual step should disappear.

Now add one exception. What happens if a customer changes size, cancels before collection or asks for an item that has just sold in the shop? Note who checks the records and who tells the customer. A workflow map is more useful when it shows these decisions as well as a successful order.

Bring your map to a Storizone workflow conversation. Ask to see one product's information, its storefront presentation and the relevant order and stock records in a supported demonstration environment.

Ask what is manual, what needs configuration and when a stock change becomes visible. If a refresh, wait or extra step is needed, include it in the walkthrough. Also ask what the team should do when the normal path cannot be completed. A polished screen alone does not answer those questions.

Choose the first improvement by naming one repeated task and the person responsible for it. That gives the next conversation a clear purpose: evaluate the flow your shop needs, with its scope and limits visible.