Why one switch is no longer enough
For a long time the order question had two answers. A Shopify order became a sales order in Zoho, or it became an invoice. We wrote about that choice in sales order vs invoice, and the reasoning there still holds.
What that choice could not express is time. Plenty of businesses want a sales order the moment the order is placed, because the warehouse works from it, and an invoice later, when the money has actually arrived. Others want both documents at once so finance and operations each have their own record from the first minute. A single either-or switch forces those stores to pick the less wrong option and fix the rest by hand.
Zync now models this as a document flow. You will find it under Orders, on the Documents & Accounting tab, in the Documents section, as the setting Create each order as.
The four document flows
- Sales order. One Zoho sales order per Shopify order. Nothing else is created. This is the default and the behaviour the app has always had.
- Sales order, then invoice when paid. The sales order is created when the order syncs. The invoice is raised from that sales order once Shopify marks the order paid.
- Sales order and invoice together. Both documents are created as soon as the order syncs.
- Invoice only. No sales order at all. Use this when your Zoho organisation has sales orders turned off, or when you simply never use them.
Whichever you pick applies to every order that passes your filters. The first document created is the order's primary record in Zoho, and its ID is stored on the Shopify order so the two stay linked.
Sales order, then invoice when paid
This is the flow most finance teams ask for once they see it, so it is worth walking through.
A customer places an order with a payment method that is not captured immediately, say bank transfer or cash on delivery. Zync creates the sales order. The warehouse can see it and act on it. In your books there is no invoice yet, so there is no receivable for money you may never collect.
Later the order is marked as paid in Shopify. That update reaches Zync, which looks at the order again, sees that an invoice is now due, and raises one from the existing sales order. The invoice lines are tied to the sales order lines, so Zoho shows the sales order as invoiced rather than leaving the two documents unconnected.
One detail happens quietly on the way. Zoho only invoices a sales order that has been confirmed. If you save documents as drafts, Zync confirms the sales order at the moment it needs to raise the invoice, because the invoice could not be created otherwise.
For orders that are paid at checkout, the two steps happen in the same sync. You get the same end state as the together flow, just with the paid condition enforced.
Sales order and invoice together, and Invoice only
Sales order and invoice together suits stores where almost every order is paid up front and both teams want their document immediately. There is no waiting state. The trade-off is that an unpaid order also gets an invoice, so pair this flow with a payment status filter if unpaid orders should stay out.
Invoice only is the leanest option. There is one document per order and it is a financial one. Choose it when the checkout is the sale, you do not track order commitments separately, or sales orders are disabled in your Zoho organisation. Keep in mind that shipment dates and tracking are written to the sales order, so an invoice-only flow has nowhere to put them. See fulfillment tracking for what that covers.
Draft or confirmed
Right beside the flow is Save documents as, with two options.
- Draft (review in Zoho first). Documents land as drafts. Someone in Zoho checks and confirms them. This is the default and a sensible starting point while you are still tuning tax and item settings.
- Confirmed (sales order open, invoice sent). The sales order is opened and the invoice is marked as sent, so the documents are live without a manual step.
A point that causes real worry: marking an invoice as sent changes its status only. Zoho does not email the customer. Your Shopify customer will not suddenly receive a second, unfamiliar invoice because you chose Confirmed.
If you record payments, invoices cannot stay in draft anyway. Zoho only accepts a payment against an invoice that has left draft, so Zync marks the invoice as sent before recording the payment. More on that in payments and gateway mapping.
Numbering and references
Two documents about the same sale should be easy to pair up. Zync does two things to help.
First, the Shopify order name is always written to the Zoho reference number. Search Zoho for the order name and you find its sales order and invoice.
Second, you can turn on Use the Shopify order number as the Zoho document number. The Zoho document then carries the Shopify number as its own number instead of the next one in Zoho's sequence. If Zoho rejects the number, because it is already used or contains a character Zoho does not accept, that one order falls back to Zoho's own numbering instead of failing. The order still syncs, and the reference number still carries the Shopify name.
Document defaults that shape every record
The Document defaults section sets details that would otherwise be edited by hand on every document:
- Show discounts, either On each line item or As one amount on the document.
- Default salesperson, for organisations that require one on every document. Leave it empty otherwise.
- Invoice payment terms (days). Zero means due on receipt. Empty uses the customer's own terms in Zoho.
- Add shipping as a line item, instead of using the document's shipping charge field.
- Show the SKU on each line, which puts the SKU in the line description.
- Customer notes, a template that accepts the variables
{order_name},{shop},{order_note}, and{tags}. Leave it empty to keep the standard note. - Terms and conditions, printed on each document.
None of these change which documents exist. They change what an accountant sees when they open one, which is often what decides whether drafts can be confirmed without edits.
Filters still decide which orders arrive
The flow answers what an order becomes. The Order Settings tab still answers which orders sync in the first place:
- Payment status, fulfillment status, and order source filters.
- Invoice Options, either Create Invoice for All Orders or Create Invoice for Paid Orders.
- Currency, either Shop Default Currency or Customer Presentment Currency.
An order that does not pass the filters is logged as skipped with the reason. If it later changes so that it does pass, for example an unpaid order becomes paid under a paid-only setup, the update brings it in. You do not have to go back and find it.
One interaction is worth knowing. The paid orders option under Invoice Options works as a filter on the whole order: an order that is not paid yet is held back entirely, sales order included, until Shopify marks it paid. If the point of your flow is that unpaid orders arrive as sales orders and get invoiced later, leave Invoice Options on all orders and let Sales order, then invoice when paid do the waiting.
What the flow unlocks downstream
The flow you choose decides which accounting features have something to attach to.
- Payments are recorded against an invoice. With the plain Sales order flow there is none, and the app warns you about it when you switch payments on.
- Refunds become credit notes that are applied to the invoice. Again, they need a flow that includes an invoice. See refunds to credit notes.
- Shipment dates and tracking are written to the sales order, so they need a flow that includes a sales order.
- Reconciliation compares Shopify orders with invoices when your flow creates them, and with sales orders otherwise. See month-end reconciliation.
If you want the full set, payments, credit notes, and tracking, choose one of the two flows that create both documents.
Moving from another connector
Changing how orders arrive is riskiest when a different tool has already sent some of them. The Only sync orders placed on or after date exists for this. Set it to your cutover date and live sync ignores anything placed earlier, so orders the old connector already created are not sent again.
A backfill ignores that date on purpose, because a backfill is something you ask for by date range. That lets you bring in a specific historical period later, deliberately, with a dry run first.
How to choose
- You fulfil first and collect later, or sell on terms: Sales order, then invoice when paid.
- Nearly everything is paid at checkout and both teams want documents now: Sales order and invoice together.
- You only need order tracking in Zoho Inventory and keep accounts elsewhere: Sales order.
- The checkout is the sale and you never use sales orders: Invoice only.
Start in draft, sync a handful of real orders, open them in Zoho, and switch to confirmed once they need no edits. Changing the flow later does not duplicate anything. Each order remembers what it already has, and a resync adds only what the new setting calls for.
Next step
Open Orders, go to Documents & Accounting, and pick your flow. The setting-by-setting reference is in the documents guide, and the broader picture of what lands in your books is on the accounting sync page.