Shopify part number and SKU search tables
Reviewed 2 October 2026 · By Activory
Quick answer
A Shopify part-number search table lets buyers look up the rows in a published catalog using a SKU, supplier code or alternate identifier. Table Master searches inside its embedded table, including selected hidden columns. It supports partial matching across up to three search words. The table can show the details needed to identify a part, and Shopify product tables can provide individual variant cart controls.
This search applies to the table’s included data. It does not change Shopify’s storefront search, predictive search or collection filtering.
Do you need native search or a parts table?
Start with Shopify’s built-in search if buyers can already find the right product by its full SKU or barcode. Test both predictive suggestions and the submitted results page.
Use Table Master when a specific catalog needs its own lookup table, alternate part numbers and visible details for comparing matching rows. Its search works on the data published in that table.
If you need to change the main search experience across your whole store, consider a store-wide search solution.
Help a buyer confirm the part after finding it
A returned row is the start of the decision. Show the current part number, product name and the attributes that distinguish it from nearby matches, such as size, model or revision. If a code changed, explain the relationship using checked catalog information.
Keep the lookup code separate from the code customers will order. An old supplier identifier might lead to a current code, but a possible alternative should not be labelled a confirmed replacement. Your approved catalog records must establish that relationship.
Keep alternate codes searchable
Store identifiers as text so leading zeros and meaningful punctuation remain intact. In Table Master, you can hide an alternate-code column from the default table view and separately include it in Searchable hidden columns. The documented limit is up to ten hidden searchable columns.
Only import information that is safe for the storefront. Hiding a column changes its display; it does not make its data confidential. Follow the search and filter guide for the relevant controls.
Try the cross-reference example
In the existing cross-reference tutorial, search 00045. The sample lookup code points to current code NEW-145 while the lookup column stays out of the default view.
These are fictional teaching codes. Try the result against the visible source rows and follow the setup steps to preserve the leading zeros. The example explains the lookup; it does not certify compatibility or create Shopify products.
Illustrated part lookup
Fictional public catalog records. This illustration is separate from the working Table Master example below. It does not connect to Shopify, certify compatibility or add anything to a cart.
Try a full alternate code, a short fragment or a code with no match.
One sample match. Confirm the identifying attributes before choosing a part.
| Part | Relationship | Selection |
|---|---|---|
| NEW-14520 mm · Revision A | Legacy numeric code |
Only public data belongs in a published table. Hidden columns are a display choice, not a privacy boundary.
Try three part-number lookups
- Enter
00045to findNEW-145through an alternate lookup code. - Enter
NEW-to see four matching records. Check each relationship and note to identify the right one. - Enter
ZZ999to see a no-match result.
These fictional records demonstrate search within this table. They don’t verify product compatibility or place an order.
These presets are available in Table Master. Changes apply to this example only.
Use these settings in your store
Open your table view, then select Design.
- Table colors → Design template: Ocean blue.
- Cell padding: set Top, Bottom, Left, and Right to 8 px.
- Table style → Text alignment: Left.
- Table style → Rounded corners: Medium (6px).
Save the table view. Check it in your theme. Your theme controls the font and available width.
Build a part-number lookup table
The working example uses Table Master storefront code and its original sample rows. Search 00045 for NEW-145 or ZZ999 for no match. Its data differs from the two-row illustration above. Cart controls, where shown in examples, use a sample cart; no real order is placed.
Plan for more than one possible answer
When a short fragment returns several rows, show the differences that help the buyer narrow the choice. Keep model, dimensions or revision visible where those attributes decide the fit. Use filters only when they are backed by reliable catalog data.
When there is no match, give the buyer a useful next step. Ask them to check the complete code or remove a filter, and provide your normal support route when identification still needs help. Do not silently substitute an unverified alternative.
Connect the selected row to the correct Shopify variant
For an ordering table, start from Shopify products and configure the Add to Cart column using the product import guide. Check the row’s product, variant, quantity and unit before testing the cart.
A spreadsheet reference row does not create a sellable Shopify product by itself. If the same product has several variants, make the selected variant clear and verify that the cart receives that exact option.
Keep the lookup data current
Decide who owns part-number changes and when the table is refreshed. Imported Shopify fields are a snapshot and use Sync products for refresh. If the source is Google Sheets, optional scheduled pulls run every six hours, with Sync now available for an earlier update. These are not continuous or two-way spreadsheet edits.
Test prices and availability separately from imported reference fields in the actual product-table setup. Do not assume that refreshing a supplier-code column proves every part of the ordering workflow is current.
Frequently asked questions
Can Table Master search a partial SKU?
Its Smart search supports partial matching across up to three words in the published table data. Test the actual codes customers use, including leading zeros, punctuation and short fragments. Do not assume fuzzy matching or arbitrary-length search behavior.
Can buyers search an old part number without seeing that column?
Yes. Hide the column in the table view and include it in Searchable hidden columns. Show enough public result information to confirm the current item and its relationship to the searched code.
Does this replace Shopify storefront search?
No. It provides search inside the Table Master table. Only rows included in that table can be found through that search.
Can the result add the right variant to cart?
Shopify product tables support per-variant quantities and cart controls. Configure the product import and Add to Cart column, then verify the result’s exact variant in the cart. A generic reference-file import should not be presented as automatic product or variant creation.
Does a matching part number prove compatibility?
No. Search identifies records in your supplied data. Compatibility or replacement status needs approved evidence for the relevant model, revision and other fit requirements. See the compatibility lookup guide.
Does the imported catalog stay synchronized automatically?
Imported Shopify fields need a manual Sync products refresh. Google Sheets can use optional six-hour one-way pulls or Sync now. Check the source-specific guide and verify the fields your buyers rely on.
Build your first parts lookup
Choose a small set of public catalog records with checked identifiers. Verify a full code, several possible matches and a no-match result. If buyers will order from the table, separately confirm the selected Shopify variant, quantity and unit in the cart.