A WooCommerce product ID identifies a record inside a particular store. An SKU is a catalogue code your business can assign to identify a stock item. They serve different jobs: a developer may need the store’s numeric ID, while your stock or support team may recognise the SKU. Send the identifier that the receiving system or person actually requests.
Confusion often begins with a message such as “please update product 120”. Is that a product ID, a supplier reference or a stock code? A short identifier policy is more useful than asking everyone to guess. It should distinguish the item, the exact variation and the system where the identifier is valid.
What the product ID tells you
The official WooCommerce product API reference describes the ID as a read-only integer identifying the product resource. The same reference has separate fields for the product name, URL and SKU. A product’s name or public page address is therefore not its numeric record ID.
WooCommerce’s product-ID guidance shows how to find it by hovering over a product in the admin Products screen. When a developer asks for an ID, also provide the store address and product name so they can confirm the context. Do not assume the same number identifies the same item in a separately built test or replacement store.
What an SKU adds to daily work
An SKU can be a recognisable internal catalogue reference. For a fictional clothing range, a team might choose SHIRT-NAVY-M for one sellable item. That example is only a naming illustration, not a requirement or a real client code. Agree a consistent pattern that your team can read and maintain, and keep a record of who controls it.
Use unique values when assigning SKUs. Avoid casually renaming established codes because other stock lists, exports or integrations may refer to them. First identify the systems that use a code and agree how a proposed change will be coordinated. A cleaner-looking spreadsheet is not, by itself, a reason to change a working identifier.
Separate the parent product from its variations
A variable product groups choices such as sizes and colours. Its variations have their own records; the variation API reference exposes separate variation IDs and SKU fields. If the question concerns one size, specify that variation rather than sending only the parent product’s ID.
WooCommerce’s variable-product documentation also notes that a blank variation SKU can default to the product-level SKU. Do not treat a displayed parent code as proof that each variation has its own distinct stock reference. If your fulfilment workflow needs a separate code for every sellable option, plan and verify those codes explicitly.
Keep SKU, barcode and import matching distinct
An SKU is not automatically a barcode or a globally recognised product number. The product API has a separate Global Unique ID field for identifiers such as GTIN, UPC, EAN or ISBN. Do not invent such identifiers by copying an internal stock code into that field.
For imports, check the exact tool and WooCommerce version. The built-in CSV importer documentation explains matching by product ID or SKU, with additional version-dependent rules. Extension importers can have different mappings. Review a current export and a small controlled sample before approving a bulk catalogue update; this article does not supply a ready-to-run import file.
A useful product-reference handover
Prepare one row per item your colleague needs to act on: store address, product name, public URL, parent or variation ID as relevant, SKU if assigned, and the exact option or change requested. Keep codes as text in working spreadsheets where preserving leading zeros matters. Confirm that exports still contain the expected code before passing them to another system.
Ask the recipient to identify a few sample products from that list. Include a simple product and, if applicable, two different variations. Resolve ambiguous references before allowing bulk changes. This is a practical acceptance check, not a claim that any particular integration has been tested.
Common questions
Can I use the product ID as our business stock code? A system may support that workflow, but confirm its requirements. A WooCommerce record ID is tied to its store context; an agreed catalogue SKU can make cross-team communication clearer.
Should every variation have an SKU? The right policy depends on how you manage stock and integrations. If separate sellable options need distinct stock references, assign and check distinct variation SKUs rather than assuming inheritance gives you that result.
Planning a WooCommerce store? Bring a sample catalogue and explain how products are identified in your current workflow. We can review the structure and information needed before a catalogue import, then agree the implementation scope.
