How a made-to-order home textile supplier absorbs retailer compliance without absorbing the cost of it.

An illustrative scenario for a curtain, upholstery and bedding maker whose retail customers each impose their own labelling, packing, EDI and delivery-window rules — and whose margins quietly disappear into meeting them.

Istanbul and Bursa corridor, Türkiye Made-to-order, multi-retailer, seasonal ranges Typically phased over 12–16 weeks

What this scenario focuses on

Retailer compliance

Chargebacks are a margin problem disguised as an admin problem

Made-to-order flow

Nothing is built for stock, so every delay is a customer delay

Seasonal changeover

Ranges turn over more quickly than the systems tracking them

Delivery windows

Early is as wrong as late when the retailer books the dock

Premium home textile showroom with folded fabrics

The Challenge

Every retailer is a different rulebook for labels, cartons, ASNs and delivery windows, and all of that knowledge lives with a handful of people rather than in the order.

The Solution

Encode each retailer's requirements against the customer record so packing, labelling and despatch documents are produced from the order rather than remembered.

What Changes

No outcome is claimed, and how much a given supplier gains depends on how heavily its retailers penalise. What changes structurally is that compliance stops depending on individuals. When the rules sit in the customer record, the correct label and the correct document are the default output of the order rather than the reward for remembering.

Challenge

The rulebook lives in people's heads

This archetype rarely fails at making things. It fails at the terms of trade. One retailer wants a specific barcode symbology and a carton weight limit; another wants an advance shipping notice transmitted before the truck moves; a third measures delivery against a two-hour dock booking and treats an early arrival as a miss. Each rule is reasonable. Collectively they form a body of knowledge that lives in a few experienced heads and nowhere else.

So the deductions arrive. A carton is labelled to last season's specification, a delivery lands a day early, a packing list does not match the ASN, and the retailer takes a slice of the invoice. Because the deductions are booked as a finance adjustment rather than traced to a cause, the business never sees that a whole account is being served at a margin it would refuse if it could see it.

Key pain points

Retailer-specific labelling, packing and EDI rules are informal knowledge, not order data
Deductions and chargebacks are absorbed into finance without a traceable cause
Made-to-order lines have no buffer, so a fabric delay is immediately a customer delay
Seasonal range changeovers strand fabric and trims nobody has re-costed

Solution

The retailer's rules become part of the order

The customer record is where this starts. Each retailer's requirements — label format, carton constraints, documentation, the delivery window and how it is measured — are encoded once, against that customer. From then on the packing instruction and the despatch documents are generated from the order rather than recalled by whoever is on shift.

Planning is then built around the delivery window rather than the despatch date, because for these retailers the window is the commitment. Fabric and trim availability are checked against that window at the point of order confirmation, which is the last moment at which a promise can still honestly be changed.

What we deployed

Retailer compliance rules held against the customer record, not in memory
Packing lists, labels and shipping notices generated from the order
Planning driven by the retailer's delivery window, not the factory's despatch date
Fabric and trim availability checked before the order is confirmed
Deductions coded to a cause so they can be traced back to a process

Order ManagementProduction PlanningInventory ManagementLogisticsQuality ControlFinancial Management

What changes

What actually changes

The second change is that deductions acquire a cause. Once a chargeback is coded rather than absorbed, the business can see which account, which process and which range produce them — and can decide, with real numbers of its own, whether an account is worth keeping on its current terms.

How you would know it is working

We deliberately do not publish outcome numbers for this scenario — they would be invented. These are the measures worth tracking in your own business instead.