INZOLY

Reseller SKU guide

A stable SKU. An exact location. No treasure hunt.

Separate permanent product identity from changeable storage, quantity, pricing, and marketplace details.

Build the SKU system

Six practical steps

Design for the catalog you want to grow into.

  1. 1
    Step 1

    Give every product one stable SKU

    Create a unique internal identifier when inventory is received. Keep it short enough to read and type, but never reuse it for a different product.

  2. 2
    Step 2

    Avoid facts that can change

    Do not build price, quantity, marketplace, listing status, or storage location into the permanent SKU. Those details can change while the product identity remains the same.

  3. 3
    Step 3

    Create a location code system

    Label rooms, racks, shelves, totes, or bins with unique codes such as R02-S03-B12. Use one documented format and make every physical label easy to scan or read.

  4. 4
    Step 4

    Store private inventory details

    Keep cost, source, acquisition date, supplier notes, location, and internal condition checks in the product record—not in buyer-facing listing copy unless disclosure is actually relevant.

  5. 5
    Step 5

    Reuse the SKU across listings

    When a marketplace supports seller SKUs, use the same internal product SKU so listings can be matched back to one catalog record. Verify each channel's current field rules.

  6. 6
    Step 6

    Audit before inventory grows

    Check for duplicate SKUs, missing locations, products sharing one physical spot incorrectly, unreadable labels, and marketplace listings that no longer match the master record.

Keep these fields separate

SKU
A unique, stable internal product identifier that is never reassigned to a different item.
Storage location
The current room, rack, shelf, tote, or bin code; update this field when the item moves.
Quantity
The current available units tied to the product record, with marketplace handling reviewed separately.
Cost and source
Private acquisition cost, source, date, and preparation details used for internal reporting.
Marketplace references
Channel-specific listing or item identifiers connected to the same master product where supported.

Barcodes support the identifier

A barcode can encode or reference the internal SKU, but the printed label does not replace a reliable product record. Barcode sold history is planned for Inzoly and is not presented as a live feature.

Review the inventory guide

Frequently asked questions

Reseller SKU questions

What should a reseller SKU look like?

Use a short, unique sequence your operation can maintain, such as INV-000184. Category or acquisition-year prefixes can help only if they will remain accurate and will not create unnecessary complexity.

Should the storage bin be part of the SKU?

Usually no. A product can move while its identity stays the same. Keep the stable SKU and editable storage-location code in separate fields.

Can the same SKU be used on multiple marketplaces?

Use the same internal product SKU in seller-SKU fields where each marketplace supports it, but verify current formatting and uniqueness rules. Marketplace listing IDs remain separate channel-specific identifiers.

Does Inzoly show sold history by scanning a barcode?

Not yet. Barcode-based sold-history lookup is planned. Current product records can organize SKUs, quantities, sources, acquisition dates, locations, and marketplace references without promising that future scan workflow.

Keep product identity and location connected.

Use structured product records to organize SKU, quantity, source, acquisition date, and storage location across a growing catalog.

Explore inventory software