Your commerce evaluation should follow the order.

Look past the checkout

A checkout is one moment in a longer commercial workflow. Start your evaluation by following a real order from the product information the customer sees to the operational work your team completes.

Choose a common order and one that creates an exception. Keep the examples specific enough that a product team can show how its software would handle them. A list of features is less informative than a complete journey.

Agree on what belongs in the catalog

Write down the information your team needs to sell each product. Include the identifiers, variations and channel-specific information that affect your actual business. Then note who owns updates.

If information appears in more than one selling channel, include a change scenario in the evaluation. Ask how the change is represented, which connections are supported and what a merchant sees when an update needs attention.

Treat payment state as a separate question

An order and a payment are related, but the operational decisions around them need to be explicit. Describe what your team does while a payment is pending, after it succeeds and when an exception occurs.

Ask a supplier to identify the payment providers it actually supports and explain where the provider’s responsibilities begin. An orchestration feature does not by itself establish payment-provider coverage or settlement behavior.

Test an online order returned in your shop

Consider a hypothetical retailer with a physical shop and its own online store. A customer brings an online purchase back to the shop. Ask a supplier to trace the original order and payment, confirm the applicable return policy and record the condition of the item.

Follow the stock decision separately from the refund. An item physically back in the shop may still need inspection before it can be sold again. Ask which location receives it, whether it is held aside or made available, and what the online store shows afterward. Then ask how the team distinguishes stock reserved for another order from stock available for a new sale.

Now follow the refund request and its outcome. A stock adjustment alone does not show that a refund succeeded; a refund alone does not establish that an item is fit to resell. Ask who checks each result and what they do when one update is delayed or fails.

Record the evidence for your actual channels, hardware and connections: demonstrated now, requires configuration, requires integration or unconfirmed. Give any unresolved step an owner and compare the demonstrated workflow with your current workaround.

A conversation about Ignite Commerce

Ignite Commerce is Ignite’s product for catalogs, orders and merchant operations. Discuss your selling channels, stock ownership and order handoffs with our team.

Bring your last actual stock or return incident to the conversation. Describe the shop and online store involved, the tools you use, what remained unresolved, who handled it and the workaround your team relies on. Use a description of the workflow without customer names or order details.