Sending Orders to a Production Partner Without Losing a Detail

A customer types a name into a personalization box, picks a chain length from a dropdown and pays. That data now has to travel from a checkout page to a bench where someone will cut metal to match it. Between those two points sit an export file, an email, a spreadsheet, a translation of one measurement system into another and at least two people reading quickly. Every one of those steps can quietly change the order, and none of them announce it.

Below we work through the handover failures that show up most often when a store is connected to a production partner, and what to change in the process so the piece that gets made matches the piece that was bought.

The order arrives as prose instead of as fields

The most common setup is also the weakest: a seller forwards the customer confirmation email and expects the workshop to read it. Prose hides things. A note added at checkout gets skimmed, a second item in the same order gets missed, and nobody can tell later which version was final.

Send structured fields instead, one row per item, always in the same order: your order number, design reference, metal, size or length, personalization text, font, chain type, and destination country. Same columns every time, even when a column is empty. A production sheet with a fixed shape can be checked in seconds; an email cannot.

Personalization text is retyped somewhere

Any point where a name is typed again is a point where it changes. A capital becomes lower case, a double letter drops, an accented character turns into something the file could not carry.

Move the text by copy, not by keyboard, from checkout to sheet to bench. Where a character set is involved, agree in advance what the workshop can produce and what will be substituted, and never let the substitution happen silently. What is possible with different alphabets and special characters is covered in our article on character limits in personalized jewelry.

Sizes are sent in whichever system the customer used

Orders from a US buyer, a UK buyer and a European buyer arrive in three different ring sizing systems, and a chain length can be in inches or centimeters. If the raw value goes to production untouched, someone at the bench converts it, and that conversion is now happening at the worst possible place: far from the customer and late in the process.

Convert once, at your end, and send a single agreed unit to the workshop — internal diameter for rings, millimeters for lengths — with the original customer value kept alongside for reference. Which measurement should reach production is set out in our piece on size system conversion.

Nobody confirms the order was actually read

Sending is not receiving. A file that lands in a mailbox nobody opened until the afternoon has not started production, and you will not discover the gap until a customer asks.

Build an acknowledgement step: the workshop confirms the order reference and repeats back the personalization text and size before work begins. Repeating back matters more than confirming receipt, because it catches an error while it is still free to fix. Keep the acknowledgement in the same thread as the order so both sides can find it later.

Addresses go to the workshop unvalidated

In a stockless model the shipping address travels with the production data, and it is the only version anyone has. A missing apartment number, a transliterated street name or a postcode with a stray space becomes an undeliverable parcel of a piece that fits one person.

• Validate the address at checkout rather than at dispatch.
• Keep address fields separate from personalization fields so nothing gets merged in an export.
• Agree who fixes an address that fails carrier validation, and how that change gets back into the order record.
• Never allow an address correction to arrive as a message without also updating the source record.

Changes travel outside the order record

A customer emails to change a spelling. You forward it to your contact at the workshop. The bench is working from a sheet exported that morning. Two truths now exist and the older one is in the hands of the person cutting metal.

Amendments have to change the record, not sit beside it. Update the row, mark it as revised, and get an acknowledgement against the revised version. Where an amendment is no longer possible, the answer to the customer is a decision about production, not about customer service, and it needs to come back from the workshop before you promise anything.

The export flattens what the bench needs

An order with three items where only one is personalized is where exports fail. A flattened export can attach the personalization to the wrong line, or drop the plain items entirely because they had no note.

Export at line-item level and reconcile counts daily: orders placed, rows sent, rows acknowledged, pieces dispatched. Four numbers that should agree. Anyone can check them in a minute, and they surface a lost order before the customer does. How listing-level details are held per design is covered on our made-to-order catalog page.

Descriptions drift as well. A design called a thin oval pendant on your storefront becomes a small oval in a message and a different model at the bench. Once a catalog passes a few dozen designs, prose references start producing the wrong piece entirely.

Assign a reference code to every design, agreed with the workshop, and use it everywhere: listing back-end, order file, packing slip, photography folder. When you add a metal option or a length variant, extend the code rather than inventing a new phrase. Setting these conventions early is part of a first production conversation, described in our guide to the first message to a workshop.

Fixing the handover

Every failure above has the same shape: information changed form between the buyer and the bench without anyone checking. The fix is not more messages, it is fewer transformations and one acknowledged record.

The decision rule: take a completed order at random and trace the personalization text backwards from the finished piece to the checkout field, naming every place it was copied or converted. If you count more than two, remove one before your next batch of listings goes live, because every extra hand on that text is an error waiting for a busy week.