E-commerce operations where every return, refund and order exception reaches the person who can resolve it — including your 3PL

Mi Retail is an operations center that manages the human work around your sales channels. The e-commerce platform or order management system keeps the catalog, the orders and the payments; Mi Retail handles what happens when an order needs a person — a return to inspect, a refund to approve, a failed delivery, an order held for review, a price error on a channel. Each of those situations becomes an Operational Work Item with an owner, a state, a due date and evidence, and it travels between customer care, e-commerce, fulfillment partners and finance until it is resolved. The team sees what is stuck and why, and customers stop being the ones who chase it.

No. Your e-commerce platform stays the system of record for catalog, checkout, orders, payments and refunds, and Mi Retail never charges a card or issues a refund on its own. What it covers is the part the platform was not built for: coordinating the people who must act when an order leaves the happy path. The platform can tell you a return was requested; Mi Retail manages who inspects the item, who approves the refund, what happens to the product and with which evidence the case closes. Keep your e-commerce platform; Mi Retail takes over where the work leaves it and records who did what, and when.

When a customer asks to return an item, customer care opens a return work item from the order, with the reason, the customer’s photos and the return label. When the parcel reaches the warehouse or a store, an inspection work item is created there — derived to your 3PL if they run the warehouse — and the item is graded against your return conditions. With the grade in front of them, the e-commerce manager approves the refund and decides the item’s disposition. Customer care issues the refund in the platform and tells the customer, the warehouse restocks or scraps the item, and finance books any write-off. Every step has an owner and a state, and the return closes with its full evidence.

Yes. Work between companies moves as derived work items, so both your brand and your 3PL need their own organization on Mi Retail. You pick the 3PL from the directory and send the inspection or disposition; it lands in their own intake queue, and they assign it inside their warehouse teams. Each side keeps its privacy: you follow the state, due time and result — the photos, the grade, the stock receipt — but not their internal projects or conversations, and they see only what you shared. When they close their derived work item, your return is updated and can move on. The same works with a marketplace partner, a repair service or a carrier handling a damage claim.

Routine refunds inside your policy can be closed by customer care directly, with the reason recorded. A refund that exceeds an agent’s limit, falls outside the return window or depends on an inspection becomes an approval work item in the approver’s queue, with the order, the customer history, the photos and the inspection grade attached. The approver decides from the work item, and the decision is recorded with its reason. If the due date passes, the coordinator sees it at risk and can reassign or escalate it, and the next level receives the same context instead of a forwarded thread. Leadership only sees the refunds that truly need them, not every routine case.

The decision is part of the return, not an afterthought. Once the item is inspected and graded, the approver chooses its disposition — back to sellable stock, open-box, refurbish, return to vendor or write-off — and that choice travels as a work item to whoever holds the item, whether a store, your own warehouse or a 3PL. They execute it and close it with a stock receipt or a disposal record. If the item is written off, finance receives a review with the inspection grade, the photos and any carrier or supplier claim, so the loss is booked with its cause. Over time, repeated write-offs of the same product become findings for merchandising or the supplier.

Any order or channel situation that needs a person can become a work item. A failed delivery or a wrong address becomes a follow-up with customer care and the carrier. An order held by fraud screening becomes a review with a due time, so a legitimate customer is not left waiting. A price or promotion published wrongly on a channel becomes an incident for pricing or merchandising, with the affected orders attached. A product listing rejected by a marketplace becomes a request for the catalog team. A loyalty or gift card dispute becomes a case with its evidence. The platforms keep doing what they do; Mi Retail makes sure each exception has an owner and a result.

Every work item keeps who acted, when, what they decided and which documents supported the decision. When a customer disputes a charge or claims an item never arrived, the team can show the full trail of the order’s exception: the customer’s photos, the return label, the warehouse inspection with its own photos, the approval with its reason, the refund reference and the proof of delivery. Because each piece was captured while the work happened — including the parts done by your 3PL — nobody has to rebuild the case from emails and help desk threads. Control & Assurance lets finance or audit review those trails and record findings without asking anyone for screenshots.

Each role gets its own surface on the same operation. Customer care agents work from My Work, which shows the returns, refunds and follow-ups that are theirs, ordered by due time. The customer care lead and the e-commerce manager use Team Operations to see what is unassigned, waiting on the 3PL or blocked, and to rebalance the load. Finance sees the write-offs and return costs it must review. The head of e-commerce looks at Operational Portfolio for returns by age, refunds at risk and partners that miss agreed times, and Executive Operations shows only what needs a decision at that level, such as a product with repeated damage claims. Nobody has to read the whole help desk to understand the operation.

The Commerce suite is for the function that sells: the channel, the order, the price, the promotion, the return and the refund, whether the sale happens online, on a marketplace or at a counter. The Retail edition is for running physical stores: shifts, cash sessions, shelves, replenishment, cycle counts and store checklists. Many companies use both. In Mi Retail the work items from each meet in the same operation: an online return inspected in a store starts in Commerce and is executed by store associates, and a pickup order with a missing item starts in Retail and can end in a refund handled by the commerce team. Each team sees its part without switching tools.

The Commerce suite of StoneOS brings apps for the domain work of selling — Catalog, Pricing, Promotions, POS, Checkout, Orders, Returns, Loyalty, Gift Cards and Channels — on top of the Business Core apps every team uses, such as Chat, Docs, Sheets, Drive and To-do. Those apps keep the depth of each domain: Orders holds the order, Returns records the return and its grade, Pricing and Promotions govern what each channel shows. Mi Retail is where the work they generate meets the people who must act on it: an inspection, a refund above the limit, a disposition or a pricing incident lands as a work item in the right queue. If you keep your current e-commerce platform, it stays the record.

Yes, it is the same product at both ends. In a small online brand, the founder often answers customers, approves refunds and ships replacements, and the experience collapses to one Today view with the returns waiting, the refunds promised and what the 3PL still owes, without approval chains that do not exist. In a large omnichannel retailer, the same work items are split across customer care, e-commerce, merchandising, stores, several fulfillment partners and finance, each with its own surface, and exceptions escalate to the right level. As the brand grows and adds channels or warehouses, the same work items start moving between more people, and nothing has to be migrated or redesigned.

Start with returns, because they cross the most people: customer care, the warehouse, an approver and finance. Create a returns workspace, invite those people and, if a 3PL runs your warehouse, invite them to create their own organization so inspections can be derived to them. Open the next returns as work items instead of emails and let them move. Within a few weeks you will know where returns wait, how long refunds take to be approved and which products keep being written off. Then add other order exceptions, connect the e-commerce platform you already use and, when it fits, bring in the Commerce suite apps from StoneOS. Mi Retail is free to start, so one flow can prove it.