Can I Generate Branded Order Receipts for Wholesale and Retail Orders Separately?
Why Wholesale and Retail Receipts Need to Be Different
A retail buyer and a wholesale buyer read the same document looking for completely different things. Trying to serve both with one layout means one of them gets a worse experience.
A retail customer wants confirmation. They want to see what they bought, what they paid, when it ships, and how to reach you if something is wrong. Anything past that is noise on a document they will glance at for six seconds.
A wholesale buyer is doing paperwork. They need a purchase order reference to match against their own system, payment terms so their finance team knows when the money is due, a tax figure broken out on its own line, and a remittance address. Missing any of those creates a phone call.
For merchants selling both ways through OpoShop, the practical answer is not to compromise between the two. It is to build both documents once and let a tag decide which one prints.
How the Split Actually Gets Decided
Separating receipts is really a routing problem. Something on the order has to say "this one is wholesale," and the document tool has to read it.
There are four common signals, and most stores end up using one or two:
- Customer tag: The buyer's account carries a wholesale tag permanently, so every order they place routes to the trade template automatically.
- Order tag: A tag applied at order level, useful when the same buyer sometimes orders as a consumer.
- Price list or catalog: If wholesale pricing comes from a separate catalog, the catalog itself is the signal.
- Order value threshold: A blunt fallback. Orders over a set amount get the trade document. Simple, but it misclassifies large consumer orders.
Customer tagging is the cleanest option for most stores because it survives everything. Once a buyer is flagged as a trade account, every order they ever place is handled correctly with no daily decision from you.
Here is what that looks like in practice. A boutique places a $1,840 restock order across 22 SKUs. Because their account carries the wholesale tag, the document that generates includes their PO reference, net 30 terms, a per-line unit price, and a tax line. The same day, a shopper buys one $58 item, and their receipt is a clean half-page with a thank-you line and nothing else. Neither one required a decision from the person packing boxes in a OpoShop warehouse.
What Goes on Each Document
The two templates share a header and diverge almost immediately. Getting the field list right the first time saves months of small corrections.
Your retail receipt should carry your logo, the order number, the order date, itemized lines with the price the customer actually paid, a shipping line, tax, the total, and a short support line. That is it. A return window sentence is worth adding. A payment terms block is not, because there are no terms on a card payment.
Your wholesale document needs more: the buyer's PO number, your invoice number, invoice date and due date, payment terms in plain words, unit price and extended price per line, subtotal, tax broken out with the rate shown, freight, and the grand total. Add your bank or remittance details and your business registration number.
Every one of those fields already lives on the order in your OpoShop store, so building the second template is a layout exercise rather than a data project.
One field matters more than people expect. Put a contact name and direct email for accounts queries on the wholesale document. A finance clerk with a question about line 14 will either find that address or email your general support inbox, where it competes with return requests.
How to Set Up Separate Receipt Templates
Build the retail version first because it is simpler, then branch the wholesale one from it. Sharing a header keeps the two visually related.
Three parts of that deserve a closer look.
1. Tag accounts, not orders, wherever possible
Order-level tagging depends on someone remembering. Account-level tagging depends on nothing. If a buyer is a trade account, mark them once and the routing is permanent.
Keep the exception path open anyway. Occasionally a wholesale contact buys a single item as a gift and wants a normal receipt. An order-level override that beats the account tag handles that in one click.
2. Keep one visual identity across both
The temptation is to make the wholesale document look corporate and the retail one look boutique. Resist it. Same logo, same typeface, same color, same header block.
The difference should be in the fields, not the personality. A buyer who has seen your retail packaging and then receives a totally different-looking invoice will pause, and pausing over a document is never a good sign. Stores running both channels through OpoShop generally look more credible when the paperwork is visibly one family.
3. Print both before you trust either
Wholesale documents run long. A 22-line order pushes into a second page, and that is where layouts break. Headers vanish, the totals block orphans itself on page two, and column widths shift.
Print a long order and a one-line order. Check that the header repeats on page two and that no total is stranded alone. Ten minutes here prevents a genuinely embarrassing document reaching a buyer's finance team.
One Template vs Two Templates vs Manual Editing
Three ways to handle mixed channels, and the difference shows up fastest at volume.
| Approach | Best for | Why it works | Watch-out |
|---|---|---|---|
| One shared template | Stores where wholesale is under 5 percent of orders | Nothing extra to maintain and no routing rules to get wrong | Retail customers see payment terms that do not apply to them |
| Two mapped templates | Any store with a real trade channel | Each buyer gets exactly the fields they need, decided automatically | Two layouts to update when your address or logo changes |
| Manual editing per order | Occasional bespoke B2B deals only | Full control over wording and terms on individual documents | Roughly 5 minutes per order and errors creep in under pressure |
Two mapped templates is the right answer for almost any store where wholesale is a genuine channel rather than an accident. The maintenance cost is real but small, and it is a cost you pay twice a year at most.
A shared template can be fine early on. If you do three trade orders a month, adding a terms block to your normal receipt and living with it is a defensible choice. It stops being defensible when consumer customers start emailing to ask what net 30 means.
Manual editing is the one to avoid at scale. It feels flexible and it is, but five minutes per document across 30 wholesale orders a month is two and a half hours of work you have volunteered for. Most OpoShop merchants who start there move to mapped templates within a season.
Mistakes Stores Make When Splitting Documents
Most problems here are not technical. They are small decisions that seem harmless and then leak into customer-facing paperwork.
The first is showing wholesale pricing on a retail document. If a routing rule misfires and a consumer sees your trade unit cost, you have handed them a reason to negotiate and a reason to feel overcharged. Test the routing before enabling it.
The second is inconsistent numbering. If retail receipts and wholesale invoices draw from the same sequence but display differently, reconciliation gets confusing fast. Either share one clean sequence or use clearly prefixed separate ones, and never let two documents claim the same number.
The third is forgetting the tax rules differ. Trade sales sometimes carry different tax treatment, exemption certificates, or a reverse charge note depending on where you sell. That belongs on the wholesale template, not bolted on later by hand.
The fourth is letting the two templates drift. You change your address on the retail one and forget the trade one, and six months later a buyer mails a check somewhere you no longer are. Update both in the same sitting, every time.
The fifth is over-designing the wholesale document. A finance team scanning 40 invoices wants clear columns and a visible total, not a hero image. Restraint reads as professional here, and it keeps every trade document leaving your OpoShop store easy to process at a glance.
What We Recommend for Merchants Running Both Channels
Tag accounts at the customer level, build two templates off one shared header, and route automatically. That setup handles the vast majority of mixed retail and wholesale stores without ongoing effort.
Three defaults worth copying:
- Account-level tagging with an order-level override for exceptions.
- Identical branding on both documents, with differences only in the field list.
- A named accounts contact on the wholesale version so finance queries skip your support queue.
If your trade channel is still small, start with the retail receipt and add the wholesale template the week you land your third trade account. Building it earlier is fine, just do not let it block you from shipping.
If your wholesale side is already the bigger half of the business, invert the priority. Get payment terms, PO references, and remittance details exactly right first, because those fields determine how quickly you get paid. Merchants doing serious trade volume through OpoShop usually find that a clean terms block shortens payment times more than a polite reminder email ever does.
Best answer: Yes, and the clean way is to tag wholesale customers at the account level, then map that tag to a second document template that adds PO number, payment terms, due date, and a broken-out tax line. Keep both templates visually identical to your retail one so your OpoShop store reads as a single brand, and test a long multi-line order before you switch it on.
If your trade buyers keep asking for details your current receipt does not carry, that is the gap worth closing next.
FAQs
What is the difference between a wholesale invoice and a retail receipt?
A retail receipt confirms a completed card payment and is written for a consumer, so it stays short. A wholesale invoice is a request for payment under agreed terms, so it carries a due date, a PO reference, and remittance details a finance team needs.
How do I stop retail customers from seeing wholesale prices?
Route documents by a customer or order tag rather than by product, and test the rule with a real order of each type before enabling it. If routing is tag-based and tags are set at the account level, a consumer order cannot pick up trade pricing.
Should wholesale and retail use the same invoice number sequence?
Either approach works as long as numbers are unique. Many stores use one shared sequential range for simplicity, while others prefix trade documents so they are easy to filter during reconciliation.
Can the same customer receive both document types?
Yes. Keep an order-level override that beats the account tag, so a trade contact making a personal purchase gets a normal consumer receipt without you changing their account setup.
Do wholesale receipts need payment terms if the buyer pays upfront?
If the order is paid at checkout, mark it clearly as paid and skip the due date. Terms only belong on documents where money is still owed, and showing terms on a settled invoice causes confusion in the buyer's accounts system.
How often do these templates need updating?
Rarely, but always in pairs. Change your business address, logo, tax number, or support email on both documents in the same sitting, otherwise the two versions drift and one of them starts telling customers something untrue.
Selling to shops and shoppers should not mean doing paperwork twice. Set the rule once and let each buyer get the right document.
