Price the Recordkeeping Behind a Custom SKU

A custom SKU can carry a healthy gross margin while requiring work that the quote never priced. Someone must maintain its approved requirements, supplier options, change history and relationship to the products that use it.

That work begins with launch and continues when the customer changes artwork, the supplier changes a material or the plant needs a substitute.

Give the item an authoritative record

For a proposed custom package or ingredient, identify the approved revision, applicable products and sites, qualified sources, acceptance requirements, supporting evidence and change authority.

Link to the underlying records rather than copying the same specification into several spreadsheets. Purchasing needs to know what it can order. Production needs to know what it can use. Quality needs to know which approval applies.

A filename is not an approval state. Distinguish draft, approved, superseded and pending review in whatever system the team already maintains.

Estimate the recurring work

Ask what makes this item different from an existing family. Does it require separate samples, artwork approval, supplier reviews, purchasing releases or inventory reconciliation? Which of those recur, and who performs them?

Use the team's actual workload to estimate cost. Avoid allocating an equal administrative charge to every SKU if some share records and others need individual attention.

For a hypothetical custom sleeve, the design may take little time while each artwork revision creates unused stock and a new approval round. The relevant commercial question is how frequently the customer expects changes and who carries that exposure.

Put the choice in the quote

The options may include a customer premium, a minimum economic run, a shared specification or a different replenishment arrangement. Declining a customization is one option, not the default conclusion.

Give sales a concrete comparison: expected contribution after the recurring work and inventory exposure, plus the strategic reason to accept an exception.

Review existing custom items when their requirements change. A record that was complete at launch can become unreliable later. The purpose is to keep the commercial promise connected to the work required to keep delivering it.