Your Marketplace Order Number Is Not Automatically Your Invoice Number
A marketplace order number and an invoice number look like the same kind of thing and are not. The order number is the platform's identifier for the transaction; the invoice number is your identifier for your document. Print both on your invoice, keep your own sequence unbroken, and never let one stand in for the other.
The confusion is understandable: both numbers arrive attached to the same sale, and both look like references. But they answer to different owners. The order number belongs to the marketplace — it is unique inside their system, meaningless outside it, and ordered by their clock, not yours. The invoice number belongs to you — it is unique inside *your* records, runs in your sequence, and is the number your accounts, your tax folder, and your customer references all point at.
What breaks when you use the order number as your invoice number
- Your sequence stops being a sequence. Marketplace numbers are long, random-looking, and shared with direct sales that have none — your own archive becomes unsortable and gaps become unexplainable.
- Direct sales fall out of the system. The wholesale order and the market-stall sale have no marketplace number; a numbering scheme built on borrowed numbers has nothing to give them.
- Two platforms collide. Marketplaces do not coordinate their numbering with each other; lean on both and duplicates are a matter of time.
The working habit costs nothing: your invoice carries your number in the number field, and the marketplace order number goes in the notes or a reference line (“Order #88412”). Either system's search then finds the document — the buyer quotes your number, the platform quotes theirs, and both land on the same page. It is the same dual-key thinking the wholesale guide applies to a buyer's purchase order reference, and it is built into the annotated seller template. Your sequence stays yours: set it once in the maker — the remember box keeps your shop details and numbering in your browser between orders.
A tale of two searches
Picture April. A buyer messages: “Can you resend the paperwork for order #88412?” With borrowed numbering, you search your files for 88412, find nothing (your documents are named by platform downloads and good intentions), and reconstruct the sale from the platform screen while the buyer waits. With your own sequence and the reference printed on the document, the same search takes seconds: your archive is indexed by your numbers, the reference ties the match, and the PDF you resend is the very document you issued in November — identical, because originals never change.
The reverse search matters just as much. Your accountant asks about invoice FI-0117; the buyer, asked the same question, knows it only as “the candle order”. Because your document carries both numbers, either party's question lands on the same page. Dual-keying is a tiny habit with an outsized payoff: it makes your paperwork bilingual, fluent in your system and in every platform's, and it costs exactly one extra line per invoice for the whole of your selling life.
One more place the distinction pays: your own reference when a buyer pays by bank transfer. Ask them to put your *invoice number* — not the platform order number — in the payment reference, because your records are indexed by your sequence. A transfer that arrives wearing your number matches itself; a transfer wearing a platform's order number sends you back into the marketplace screens to translate. The request costs one line in the notes of the first invoice you share with any direct buyer, and after that it is simply how your paperwork works.