Create stock codes that survive a growing product range

A stock code is an internal identifier. Its value comes from being unique, stable and connected to the correct item—not from containing every detail about the product.

If your shop currently uses “blue bag,” “new blue bag” and “blue bag final,” start by separating public names from internal references. Customers should see understandable product names. Your records need a dependable way to distinguish the exact sellable choices behind those names.

Decide what receives its own reference

Begin with the unit you manage separately. Different sizes or colours may require different stock references if they have independent quantities. A pack may need its own reference if you receive and sell it as a pack.

Do not assign separate references merely because the same item appears in two marketing collections. A summer collection and a gift collection can point to the same physical stock. Creating two unrelated balances can make one item look like two.

For components and finished bundles, decide how the relationship is recorded. A bundle reference does not create additional pieces of its components.

Choose a format you can maintain

A short sequential reference can work well. A structured reference can also work if the structure remains understandable. The important choice is consistency.

For an illustrative range, BAG-001, BAG-002 and BAG-003 could identify three sellable variants. A private lookup supplies the full meaning. You do not need to encode the current price, supplier, season and material into every code.

Avoid characters that are easily confused in your workflow. Check any restrictions imposed by the systems, printers or import tools you use before assigning a format across the catalogue.

Keep a controlled lookup

Create one place where a reference maps to its current description and counting unit.

These are examples, not prescribed identifiers or a statement about oBizee's fields. Keep supplier references separately if they serve a different purpose.

Do not put customer information inside stock codes. Codes may appear on labels, exports and shared operational documents.

Assign codes before importing quantities

Check the list for duplicates and missing variants before entering stock. Two items sharing a reference can create more damaging confusion than two items sharing a similar display name.

If you already have records, build a mapping from old identifiers to new ones. Do not replace references in active orders without understanding how your system links those orders to products.

Keep a copy of the mapping and use an authorised migration process for software changes. Renaming a spreadsheet cell is not necessarily the same as safely changing a system identifier.

Make the physical location match the record

Label storage positions or containers clearly enough that a helper can find the right item. A code on a sheet is useful only if the physical stock can be identified.

Where several variants look similar, include a human-readable description next to the internal reference. This helps catch a misplaced item before it becomes a wrong dispatch.

Do not assume a handwritten label is a scannable barcode. If you need scanning, verify the tool's actual barcode requirements and test the printed result.

Preserve history when products change

A marketing title can change without changing the physical item. In that situation, preserve the stable identifier and update the description in a controlled way.

A materially different product may require a new reference, particularly when old and new stock coexist. Record what changed so packing and support do not treat incompatible versions as interchangeable.

Retire discontinued references rather than immediately reusing them for unrelated items. Historical orders and adjustments should remain understandable.

Check whether the system works in practice

Ask somebody to locate a variant using the record, identify its counting unit and connect it to a sample packing instruction. Watch where they hesitate.

Then inspect a receipt, sale, return and count correction. The same reference should identify the same item across those events. If it does not, fix the mapping before adding more codes.

Use the stock guide for quantity states and catalogue preparation for public product information. The best coding system is one your team can use reliably as the range grows, not the most elaborate code you can invent today.