Bring order details, payment status, and fulfillment into one workspace. Give your team the context to prepare a shipment, answer a customer, and handle what needs attention.
Part of Tanqory Commerce Core
Review orders from your Tanqory storefront and supported API workflows together. External sales channels require their own integration; a shared order view does not replace financial reconciliation.
See what the customer ordered, the selected variants, and the information needed for the next step.
Evaluate the connector for each marketplace before planning an order import. Broader marketplace connections are part of our development direction.
Retail and POS are part of our wider platform direction. Confirm the released connection and supported workflows before including them in your operations.
Developers can evaluate supported order endpoints and their permissions for a custom connection. Access and behavior depend on the endpoint, not just the integration name.
One place to review the order information your team works from.
A typical physical-product order involves several different kinds of progress. The stages below explain the work; they are not a list of exact system statuses or automatic actions for every order.
Clear order information. Deliberate decisions. Better handoffs.
Check the items, quantities, customer details, and delivery information. An order being created does not by itself mean its payment succeeded.
Review the payment result before taking the next action. Authorization, capture, settlement, and a payout to your bank are separate steps.
Confirm the items and location for fulfillment, then organize picking and packing. The available actions depend on the order and your shipping setup.
Keep shipment and tracking information connected to the order. A shipped order is not the same as a confirmed delivery.
Review cancellations, returns, or refund requests against the order and your policy. Returning an item, issuing a refund, and restocking are separate actions.
Use the order record as the starting point when payment, stock, delivery, or a customer request needs attention.
Know what changed before deciding what to do.
Check the payment status and provider response before retrying or asking the customer to pay again. An unclear result should be investigated before another charge is attempted.
→ Decide from the payment record, not an assumption.
Review the product, quantity, and location involved. Agree on an available option with the customer before promising a replacement or a different delivery date.
→ Give the customer a clear, realistic next step.
Check the address and current shipment stage. Confirm which details can still be changed and whether the carrier must be contacted.
→ Use current delivery information to resolve the issue.
Identify the items ready to ship and those still outstanding. Use the supported fulfillment actions and explain any separate shipments to the customer.
→ Keep shipped and outstanding items distinguishable.
Review the request against payment and fulfillment progress. Confirm what can be changed before cancelling, editing, or committing to a refund.
→ Make the change with the right order context.
A return, a refund, and a replacement solve different problems. Start with the items, amounts, and outcome agreed with the customer.
Review which items and quantities are involved, their condition, and the applicable return policy before deciding the next action.
Check the refundable amount and available refund method before confirming. A submitted request is not proof that the customer has received the money.
Confirm stock, any price difference, and the delivery arrangement. Choose the supported order workflow rather than assume an exchange happens automatically.
Inspect returned items before putting them back into sellable stock. A refund alone does not establish that inventory is ready to sell.
Use the items, location, and delivery requirements to organize the work that follows a sale.
Review the order location and the stock available to the team preparing it. Shipping choices depend on your configured locations and services.
→ Make the fulfillment handoff clear.
Review the fulfilled and outstanding quantities. When using partial fulfillment, keep each shipment and its tracking details tied to the correct items.
→ Keep the rest of the order visible.
Review the product inventory policy before accepting an order for unavailable stock. A backorder or preorder needs a clear delivery expectation; do not assume automatic release when stock arrives.
→ Promise delivery dates you can support.
Use tracking information from the connected carrier or tracking service. Coverage and update timing depend on that service.
→ Answer delivery questions with the latest available information.
A clear handoff from order review to shipment.
Organize the working day around order status and the tasks your team needs to complete.
Narrow the list using supported filters such as order, payment, fulfillment status, and date.
Use the views available in your workspace to focus on regular tasks, such as reviewing unfulfilled orders.
Check the selected orders and the proposed action. Bulk operations still need the appropriate permissions and eligible order states.
Review which operations succeeded and which need attention. A batch submission does not mean every selected order changed.
Automation needs reliable events, clear responsibilities, and a response when something fails. These are workflow planning examples, not a list of automations enabled for every store.
Define who should act when an order is ready for preparation.
Identify who will review a customer request or a delivery exception.
Decide how unresolved payment questions should reach a person with the right authority.
Use recorded order activity to understand where the process needs improvement.
Use the workspace for daily order operations and evaluate supported endpoints for custom connections. A documented API still needs the right access and careful integration.
Review the order details, payment status, and fulfillment information before taking action or answering a customer.
Work from the published documentation for the specific operation, including accepted fields, permissions, and response handling.
For an external system, confirm the event or API interface actually available. Do not treat a proposed connector as a live integration.
Check authorization, repeated requests, and failure responses before an integration changes a live order or payment record.
Connect the workflow without losing sight of who can act.
Build a repeatable routine for reviewing orders and preparing the next customer delivery.
Bring order review and daily store work closer together as the business develops.
Keep the order, item quantities, and chosen fulfillment location clear for the people preparing a shipment.
Evaluate payment terms, approval needs, and your buying process against the supported workflow before rollout.
Start from the actual order and payment information when helping with a delivery question or after-sale request.