Wholesale invoice software is anything that can issue a document, let it go unpaid for thirty days, and still tell you on day thirty-one exactly who owes what and since when. A store checkout cannot do that, because it was built on the assumption that the money arrives with the order. Almost everything awkward about invoicing a stockist follows from that one difference.
Most brands already own two thirds of what they need and have never turned it on. So the useful exercise is not shopping around. It is listing the jobs wholesale invoicing actually requires, working out which of your existing tools already does each one, and paying only for the gap that is costing you something.
What a checkout was never built to model
Take a ceramic mug: thirty-four dollars retail, sixteen wholesale, cases of four, so sixty-four dollars a case. A shop orders eight cases. Five hundred and twelve dollars.
Six cases ship on the fifteenth; two are backordered until the next kiln run. An invoice for three hundred and eighty-four dollars goes out with the shipment, carries the shop's own purchase order number, and falls due thirty days later. One case arrives cracked, so a credit note for sixty-four dollars goes against that invoice. The last two cases ship three weeks after that, on an invoice of their own. In November the shop sends one transfer of four hundred and forty-eight dollars covering two invoices and a credit note.
One order, three documents, two shipments, and a payment that matches none of them on its own. A checkout models an order as an event that closes when the card clears. Wholesale models a stockist as an account with a running balance that never really closes. Every capability below is a consequence of that.
Terms, due dates and something that ages
The first job is to issue a document that is deliberately unpaid and then keep score.
That means a terms field on the customer record rather than on the order, so every invoice to that shop inherits net thirty without you remembering. It means a due date calculated and printed as a calendar date, because the phrase net thirty alone gives a bookkeeper nothing to diary. And it means the due date counting from the ship date rather than the order date, since an invoice raised when the order was taken quietly charges the shop for the weeks you spent making the goods.
Then the part that separates a real tool from a folder of PDFs: an aging view. One screen, every open invoice, grouped by how far past due it is — current, one to thirty days over, thirty-one to sixty, beyond. If you cannot produce that in under a minute, you do not know your own cash position, and you will find out which accounts stopped paying at the worst possible moment.
Statements are the same data pointed at the customer instead of at you. One page per account, every open invoice and credit, the balance at the bottom, sent on the same day each month. Independent shops genuinely lose invoices, and a statement recovers more money than a stern reminder ever has. The terms side of this, and what your store platform can do about it natively, is covered in shopify b2b net terms.
Purchase orders, partial shipments and credits
Three mechanics that a consumer system has no reason to have.
The purchase order number. Any buyer with an approval process — a small chain, a museum shop, a grocery group — matches your invoice against the purchase order they raised and the delivery note the receiving door signed. If those three do not carry the same number, the invoice goes into a pile marked query and stays there. The tool needs a field for their number, on the order, that prints on the invoice and the packing slip without you editing a PDF by hand.
Partial shipments. Wholesale backorders are normal, not a failure. What you need is the ability to invoice the six cases that shipped, leave the other two open on the same order, and ship and invoice them later without either duplicating the original or destroying the record of what was ordered. A system that can only invoice a whole order forces you to hold everything until the slowest line is ready, which annoys the shop and delays all the money instead of some of it.
Credit notes. A cracked case, a short count, a discount you agreed after the fact. The correct response is a credit note with its own number, referenced to the original invoice, never an edit to an issued document. Editing breaks the audit trail on both sides and guarantees an argument at reconciliation. Anything you are considering has to be able to produce one in two clicks, or you will be tempted to fix damages by discounting the next order, which is how books become unreadable within a year. The document mechanics behind all three are in wholesale invoice.
Resale certificates and the tax line
This one is invisible until an account asks about it and then it is urgent.
A shop buying to resell is generally not paying sales tax on the goods, because the tax is collected at the point they sell to a consumer. To charge them correctly you need their resale certificate or exemption document on file, valid, linked to the customer record, and driving the tax calculation on the invoice automatically.
Doing it manually works for four accounts and fails quietly at twenty. Two failure modes, both expensive. You charge tax to an exempt account, they deduct it from the payment, and someone spends an afternoon reconciling a short payment. Or you exempt an account whose certificate expired two years ago, and the exposure is yours rather than theirs.
So the capability list here is short and specific: store the document against the customer, record the state and the expiry, flag a customer as exempt so invoices calculate accordingly, and let you pull the list of certificates on file at an hour's notice. Which certificates you actually need, and the difference between the shop's reseller status and your own registration, is a longer subject handled in wholesale sales tax.
Where the invoice should actually be raised
Three layers, and it is worth being honest that none of them covers the whole job alone.
Your store platform knows the products, the case packs, the prices and the stock. If it supports company accounts and price lists, wholesale orders can originate where the inventory already lives, which removes a whole class of transcription error. What store platforms are typically weakest at is the accounting tail — statements, aging, credit notes with proper numbering.
Your accounting package is the opposite. It has been issuing invoices with terms, purchase order references, credit notes, statements and reminders since long before any of us sold anything online, and you are paying for it already because you need the books regardless. What it does not know is your stock, so an invoice raised there does not move a single mug in your warehouse.
A dedicated wholesale or order tool sits between them, usually covering both sides adequately and neither perfectly, at the cost of another subscription and a setup weekend.
| Capability | Store platform | Accounting package | Dedicated tool |
|---|---|---|---|
| Terms and due dates | Sometimes | Always | Always |
| Purchase order field | Rarely | Always | Always |
| Partial shipment invoice | Rarely | By hand | Usually |
| Credit notes | Rarely | Always | Usually |
| Statements and aging | Rarely | Always | Usually |
| Resale tax exemption | Sometimes | Usually | Usually |
| Moves your stock | Always | No | Always |
Read the table as a shape rather than a verdict, because the specifics move around every year and your own platform tier changes half the answers. The shape that holds: the order belongs where the stock is, the receivable belongs where the books are, and whatever you buy is mostly buying the bridge between them.
For a brand with a handful of accounts, the cheapest honest answer is to build the order in your store so the stock moves correctly, then let it flow into your accounting tool where the terms, the due date and the chasing live. How to run the order side of that without a dedicated system is in shopify draft orders wholesale.
Getting it into the books without typing it twice
The failure that costs the most is not a missing feature. It is the same order entered in two places.
Double entry by hand produces a specific set of symptoms. Revenue in your accounting tool disagrees with orders in your store by an amount nobody can explain. Stock says you have nine cases and the shelf has seven. An invoice exists in the books for an order that was cancelled. None of these are dramatic on the day, and all of them cost a day each at the end of the quarter.
What to look for is a sync that carries the customer, the invoice, the credit note and the payment across in one direction, with the stock authority clearly on one side. One direction matters more than most people expect — two systems both trying to be right about a customer record is worse than typing it twice, because you can at least see a typo.
Where to draw the line: sync the money automatically, reconcile the bank feed weekly, and keep the wholesale ledger separate enough inside your chart of accounts that you can see what the channel actually earns. That separation is the whole reason the sync is worth setting up, and the accounts structure behind it is covered in wholesale bookkeeping.
What to check before you pay for anything
Six questions, in the order that matters.
Does it print the buyer's purchase order number and a real due date without manual editing? If not, stop reading the feature list.
Can it invoice a partial shipment and leave the balance open on the same order?
Can it raise a credit note against an issued invoice, with its own number?
Can it show you everything outstanding by age, and send an account a statement?
Does it know your stock, or will you be adjusting inventory by hand after every wholesale order?
Can you export the customer list and the full invoice history if you leave? The answer is usually yes and occasionally no, and the occasional no is the one that traps brands.
Notice what is not on that list. Nothing about design, nothing about consolidation across entities, nothing about electronic data interchange, which is a separate project you take on only when a chain account requires it in writing. A brand with fifteen stockists needs invoices that go out on the day of shipping and reminders that go out on the day they are due, and almost nothing else.
If the honest answer is that you have too few accounts for any of this to be worth configuring, that is useful information rather than a problem. Paste your store or product link into WholesalePilot and look at the preview of retailers and distributors stocking comparable products — the mix of independents and larger buyers in that list tells you how much invoicing process you will genuinely need, because one museum shop and one grocery group ask for very different things.
Questions brands ask about wholesale invoicing software
Can a store order confirmation serve as the invoice? Usually not. It typically has no due date, no terms and nowhere to put the buyer's purchase order number, and any buyer with an approvals process will send it back. Some platforms can generate a proper invoice document from the same order, which is the specific thing to look for.
Should the due date count from the order or the shipment? The shipment, unless you have agreed otherwise in writing. Counting from the order date charges the shop for your production time and gives them a fair reason to dispute the first reminder.
What happens when one payment covers several invoices? The tool needs to let you apply a single received amount across multiple open invoices and a credit note. Without that, every partial payment becomes a manual note somewhere, and manual notes are what you lose.
Do wholesale marketplace orders need any of this? Generally not. Marketplaces usually invoice the retailer themselves, carry the terms and pay you on their own schedule, so those orders never touch your invoicing at all. That convenience is part of what the commission is buying, and it is also why marketplace volume teaches you nothing about collecting from direct accounts.