Orders & Delivery
Bring purchasing, preparation, and delivery into an understandable operating flow. HEYA’s order tools give your team a shared place to follow purchases and coordinate what needs to happen next.
Live order pipeline · 3min read
The big picture
An order changes hands several times before the customer receives it. Payment needs to be understood, the right products need to be prepared, and delivery or pickup needs to be coordinated. HEYA organizes this work around purchase records and order information, with a separate area for purchase attempts. That distinction helps your team focus on the right stage of the customer journey instead of treating every interaction as a completed sale.
A closer look
Purchase settings let you define an order-reference prefix, creating references your team can recognize and use consistently. Product, payment, and fulfillment information should all point back to that order context. When support, picking, and delivery teams speak about the same reference, it becomes easier to explain what has happened and what still needs attention.
Preparing an order requires more than changing a status. The team needs the correct products, quantities, variations, and relevant delivery instructions. Use the order flow alongside stock information and shelf mapping to make that handoff clearer. Review how the order moves through your own operation so responsibilities remain understandable when several people are involved.
The backend provides Purchases and Purchases Attempts as distinct areas. This helps your team distinguish a completed order from an attempted purchasing journey that may need a different kind of review. Keep those distinctions when interpreting activity and reporting, and investigate the relevant record before making assumptions about payment or fulfillment.
In practice · illustrative scenario
A US retailer can use an order reference to connect customer support with its warehouse and delivery staff. The support team can discuss the purchase, the picker can prepare the correct variants, and the delivery team can understand the destination without each team inventing a separate description of the order.
Good to know
An attempted checkout is not the same as a completed purchase. A separate area helps teams review that activity without assuming every attempt should be treated as an order ready for fulfillment.
Yes. Purchase Settings includes an Order Reference Prefix field. It is intended to add a recognizable prefix before the order identifier, giving your team a consistent reference format.
Your next chapter
Explore the plans, connect your catalog, and build the commerce experience your customers need.
