> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/advanced-features/inter-store-trade/sell-to-another-store.md). # Sell to another store Fill the orders your shops raise, or push allocations out to them, from a central warehouse or any other store. A central warehouse has two jobs in inter-store trade, and they arrive from opposite directions. Shops raise orders on you, and you push goods out to shops that have not asked yet. Both end the same way: you pick, pack and ship, and the receiving store's goods receipt is waiting for them. Any store can do this, not just a warehouse — the shop that lends a jacket to the shop across town is doing exactly the same thing. *** {% hint style="info" %} In Flow Assistant you send the goods from **To the stores**. See [Inter-store trade in Assistant](/docs/getting-started/software-clients/assistant/inter-store-trade.md). {% endhint %} ## Before you start * Inter-store trade set up for both stores — see [Set up inter-store trade](/docs/advanced-features/inter-store-trade/set-up-inter-store-trade.md). * Your store represented by a supplier, and each receiving store by a company customer. *** ## Fill an order a shop has raised You do not have to do anything to receive it. When a shop sends you a purchase order, or reserves from goods you have coming in, a sales order appears in your store made out to that shop's customer record. It is already confirmed, not a draft, and it names the purchase order and store it belongs to. Cover it the way you cover any sale — from stock you already hold, or against your own incoming order from a real supplier — and switch between the two as the goods actually arrive. That is your business, and it changes nothing at the other end. Then pick, pack and deliver as normal. Setting the delivery to Delivered is what tells the shop the goods are on their way and creates their goods receipt. You can also settle the sale, with an invoice or a payment method set up for it. That is optional (see [what it does to your figures](/docs/advanced-features/inter-store-trade/what-inter-store-trade-does-to-your-figures.md)). A sale that is paid straight over the counter creates the shop's purchase order and goods receipt at the same moment. {% hint style="info" %} This is the ordinary chain pattern: order 500 from the supplier, let the shops draw on the delivery as it lands, and cover each shop's line from the incoming order until the goods are physically in. {% endhint %} *** ## Push an allocation out to a shop To send goods to a shop that has not asked for them, make an ordinary sale. {% stepper %} {% step %} #### Create a sale to the shop Create a sales order, set the customer to the record representing the receiving shop, and set the delivery to that shop. {% endstep %} {% step %} #### Add the lines Add what you are sending them. Every line needs a price above zero. {% endstep %} {% step %} #### Park or confirm the sale This is the moment their purchase order is created, mirrored line for line. They can see what is coming while you are still packing it, rather than finding out when the van arrives. {% endstep %} {% step %} #### Deliver Set the delivery to Delivered. A goods receipt appears on their purchase order and it moves to On the way. Their stock is untouched until they register the receipt themselves. {% endstep %} {% endstepper %} {% hint style="danger" %} Any parked or confirmed sale to a store's customer record becomes a purchase order and a goods receipt at that store. There is no separate switch for it. If you are selling something that should **not** land in that store's stock, sell it to a different customer. {% endhint %} Ship in several deliveries and each one creates its own receipt at the other end, covering only its own lines. *** ## Changing the sale afterwards Lines you add, resize or delete reach the receiving store's purchase order straight away. Four things will stop you: | You try to | It is refused when | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | Reduce or delete a line | They have already reserved those goods for a customer. The message names the store, the purchase order and how many. Ask them to release it | | Change a line at all | You have already delivered the goods. Credit the sale instead | | Add a line, or increase one | Their purchase order is closed, cancelled or fully received. Reducing and deleting still work | | Change a line's quantity | A settled return has already credited it. Make a new sale to send more, or a new return to send less | The first of these is the one that catches people, and it is deliberate: a shop has promised those goods to a customer, and that promise is not yours to break. Ring them and let them release it. Emptying the sale of all its lines does not cancel their purchase order — it is left standing so you can add lines back. To call the whole thing off, cancel the sale. To change the product on a line, delete the line and add a new one. Products are never swapped in place. *** ## Returns When goods have already shipped, credit the sale with a return. Once the return is settled, the shop's purchase line shrinks or disappears, unless the shop has already received the goods. The return is refused if the shop has promised more of the goods to customers than would remain: ring them and ask them to release the goods first. An exchange, meaning a return that also carries new items to the same shop, is not supported. *** ## Cancelling Cancelling your sale cancels their purchase order, so nobody is left waiting for goods that are not coming. A parked sale left past its valid-until date counts as abandoned and does the same. You cannot cancel once the shop has reserved the goods for a customer, or once you have delivered them. Credit the sale instead. *** ## Two things to watch **Packages.** A fixed package cannot be on the sale at the moment it becomes linked — park or confirm it with a package on board and the whole thing is refused. Add the package after the sale is linked, and the receiving store gets the **components** rather than the package line. **Serial numbers.** A linked line is one line, never split per unit. For products that need a serial number, put one unit on each line. *Last updated 13.10.2026* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flowretail.com/docs/advanced-features/inter-store-trade/sell-to-another-store.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.