Five systems, one panel, and no second tab to open

Answering “where is my order and can I still cancel it” means reading five systems of record. None of them is the helpdesk the agent is sitting in.

• Shopify, the storefront. What was ordered, what the customer paid, and what has already been refunded against it.
• Unicommerce, order management. Whether the order has been picked and packed, and which warehouse is holding the stock.
• ClickPost, delivery. Whether it has shipped, which carrier has it, where the parcel is now, and whether a return is still possible.
• Two systems the client built themselves. Their own services, for the parts of the business the off-the-shelf platforms do not cover.
• And the helpdesk itself. The customer's history in the ticket, and what an agent has already promised them.

Every one of those is a separate product with its own login, so they sit in separate browser tabs. A customer waiting on the phone gives the agent roughly ninety seconds to reconcile them, and every tab is a chance to read the wrong order or miss a refund that has already gone out.

This is not a separate tool the team has to learn or another tab to keep open. Fordawn built it as a custom Freshworks app and installed it into their Freshdesk Omni. It appears as part of the ticket screen agents already spend their day in.

The moment a ticket opens, the sidebar reads the order number and the customer’s email or phone from it, then quietly fetches what the agent needs from every one of those five systems. No search, no copied order number, no second login.

It does not stop at showing the data. From the same panel the agent can act, and each action is carried out where it belongs:

• Cancel the order
• Start a return
• Cancel a single shipment rather than the whole order
• Correct the shipping address
• Check which warehouse has the stock
• See exactly what the customer paid, and by which method

Every one of those writes back into the system that owns the record, so Shopify, Unicommerce and ClickPost stay the source of truth. Nothing is simulated for the demo, and no shadow copy of the customer’s order is kept on our side.

The sidebar was tested end to end on the client’s own staging environment, against real orders the client picked, and every result was checked against the log the sidebar writes as it works. One of those tests followed a cancellation out of the sidebar and into Unicommerce, Shopify and the customer’s email, all of which happened within about a minute. It was watched, recorded and signed off. The order codes from those tests can be quoted as they are, because none of them carry customer information.

• Every action, against a real order. Cancellation, return, single-shipment cancellation, address edit, refund lookup and stock check have each been fired at a staging order and confirmed to land in the right place.
• The failure paths, not only the happy one. Cancel an order Unicommerce has already cancelled and the sidebar passes back that system's own message, so the agent reads the actual reason instead of a generic error.
• The agent's own typing is protected. Automatic updates to ticket fields were tested against tickets that were already partly filled in, to be certain nothing the agent had written gets overwritten.
• Everything leaves a trace. Each action writes a log line the client's IT team can search weeks later, so a question about what happened on a given order is answered by looking it up rather than by guessing.