# When one order becomes several: the multi-store purchase from the company's side

> Why an order with items from several stores becomes one order per store, when that happens, what belongs to each order and what Partial means.

Source: https://vendria.com/en/ajuda/compra-multi-loja-do-lado-do-vendedor

## Where to find it

In the **Quotes** list, a purchase that became several orders shows up as a
**Purchase** card, with the orders inside. The card opens the purchase page; the
name of an order inside it opens that order directly.

What you do on the purchase page (confirm, reject and add stores all at
once) is explained elsewhere. See [The purchase page: confirm, reject and add stores all at once](/en/ajuda/a-pagina-da-compra-acoes). This page explains why the purchase exists, when it
is born and what changes in your day to day.

## What a multi-store purchase is

Your company can sell through more than one store, each with its own CNPJ, its own
catalog and, often, its own ERP. When a customer's order has items from
different stores, it becomes *one order per store*, and the orders are linked
to each other as a *purchase*.

A purchase is the order seen from above: the sibling documents grouped in a single
place. There is no "parent order" with items of its own: the purchase is the set of
orders.

## Why an order from several stores becomes several orders

An invoice has a single issuing CNPJ, and each store bills what is its own. That
is why, with the **Multi-store cart** option turned on, an order with items from
different stores becomes one order per store. The option applies to the whole organization, sits in the
Company Settings and comes turned on.

With the option turned off, each order stays in a single store:

- on screen, when you put a product from another store in the cart, the **Change the cart's
  store?** window warns that the current cart will be cleared;
- when importing an order (on screen or through WhatsApp), when the codes
  point to a store, Dri builds everything in it, the one that matches the most codes on the order,
  and the items from the other stores stay on the quote as an issue. When the
  codes do not decide it, on WhatsApp it asks which store the quote is for.

After the split, no order carries an item from another store. Each one has its own
number, and in the purchase each order is identified by the store's name.

## How a purchase is born on the seller's side

With **Multi-store cart** turned on, a purchase is born in four ways:

- *Importing an order* (on screen or through WhatsApp) whose codes match
  products from different stores: Dri splits it into one order per store. Upper or
  lower case in the code changes nothing: *ab10298* finds AB10298. A code that
  did not find a product only goes to the store whose code pattern it follows without
  doubt; in the other cases it stays in the first order, flagged as having a store to
  be defined. See [A line from another store in a purchase: which store is this item from?](/en/ajuda/linha-de-outra-loja-na-compra).
- *Building the quote in the catalog* with products from different stores: the
  **Product from another store** window warns that the cart will be split, and on saving
  one order per store is born, all in the same purchase. When the window offers
  **Save quote and start another**, it closes what is already in the cart as a
  quote and the new product starts the next one, without splitting.
- *Adding another store* to a purchase that already exists, from the purchase
  page.
- *By the customer themselves*, when they build the cart in the portal with items from
  several stores: on sending, the cart becomes one order per store.

Items added through WhatsApp to a quote that is open in the conversation
do not split anything: they go into that quote's store, even if they are from another
store, and show up there as an issue. For Dri to split by store, send
*new order* (or tap **New quote**, when it offers it) before
sending the items. See [Build a quote by text on WhatsApp](/en/ajuda/montar-cotacao-por-texto-no-whatsapp).

## What belongs to each order and what belongs to the purchase

Each order in the purchase is resolved *by its own store*:

- the price table, the discount and the taxes are that store's: the same
  product can come out with a different price in sibling orders, and that is correct;
- the minimum order is checked store by store;
- sending to the ERP is separate: each order goes to its store's ERP, and each one
  can have a different outcome;
- a line's issues are resolved inside the order it is in.

What is born the same in all of them is what belongs to the purchase: the customer and the conditions
agreed at the moment of the split: payment, freight, delivery address,
note and the customer's purchase order.

When your company turns on **Independent orders per store**, this changes after
the split: each order gets its own customer, its own seller and its
own confirmation, and the purchase page no longer confirms everything at once.
See [The purchase page: confirm, reject and add stores all at once](/en/ajuda/a-pagina-da-compra-acoes).

## The status of a purchase

The status of a purchase is read from the orders, not saved separately. If all the
orders are in the same status, the purchase shows that status. If they are
in different situations (one confirmed and another still in draft, for
example), the purchase shows as **Partial**.

**Partial** is not an error: it only means the orders did not move together. Open the
purchase to see where each order stands.

On the purchase page, an order with no items also counts. If you added a
store to the purchase and never put items in its order, the purchase stays **Partial**
even after confirming the other orders, because **Confirm all** leaves
out the empty order. Open that order from the purchase page, add the
items and confirm it. If the store is no longer part of it, reject that order; the purchase
stays **Partial**, because confirmed and rejected are also different
situations.

## Building a purchase in the editor: one group per store

In the quote editor, when the items are from more than one store, the table
splits into *groups, one per store*, each with the store's name, its own total
with taxes and that store's minimum order notice.

Each group is a different document. That is why everything the line shows (the
stock, the packaging multiple notice, the store's ERP information and the
reading open questions) belongs to that order: a decision made in one group does not apply
to the other.

When editing a quote that already exists, with **Multi-store cart** turned on, the
table does not split: a product from another store does not go into that quote. The
**Add product from another store?** window warns that, on saving, it becomes an order from that store inside the same
purchase; in some cases it also offers **Create separate quote**, which
creates a quote just for it and leaves the one you are editing as it is.

## The multi-store purchase on WhatsApp

When the quote Dri built has items from several stores, the reply opens
with **✅ 2 quotes created!** (or whatever the number is; when something needs
review, such as many items not found or a subtotal that looks
wrong, the line starts with ⚠️), shows each store with the quote number, its
items and its total, and brings *a single link*, **See the full purchase**, to the
page of the whole purchase.

When you ask for the status of an order that is part of a purchase, Dri answers
about the purchase: *"This purchase has 3 documents:"* and one block per order. On a
very large purchase it shows the first six and ends with *"(and N more
documents in this purchase)"*.
Orders you do not have permission to see are simply left out of the reply.
See [Ask for an order's status on WhatsApp](/en/ajuda/status-do-pedido-pelo-whatsapp).

## Common questions

**Why did I send items from two stores and Dri built a single quote?** There are three
common reasons: your company's **Multi-store cart** option is turned off,
and then Dri builds everything in the store that matches the most codes; there was a quote open
in the conversation, and the items went into its store; or only the codes from one of the
stores found a product. Send *new order* and the items again; if the option
is turned off, talk to your company's administrator.

**Why does the same product have a different price in two orders of the purchase?** Each
order follows its store's price table and discount.

**Why did one order of the purchase get into the ERP and the other did not?** Sending is per
store; resolve it on the order that was left out. See [When the confirmed order doesn't get into the ERP](/en/ajuda/quando-o-pedido-confirmado-nao-entra-no-erp).

**Why is the purchase Partial?** The orders are in different situations, or
one of them was left without items; open the purchase to see each one.

**What do I do when an item landed in the wrong store's order?** Move the line to
the right store. See [A line from another store in a purchase: which store is this item from?](/en/ajuda/linha-de-outra-loja-na-compra).