Create a native reference table when this product should own and edit the data. Google Sheets is optional. Decide the source meaning and exact identities first. The ordinary creation screen sets column types and matching keys; its later row-editing grid does not change that schema.
Check the creation role
An Owner creates ordinary custom and customer-product tables and needs recent second-factor verification. The specific WooCommerce SKU mapping template is created by an Author instead; that creation does not itself publish a mapping. These permissions are alternatives for different templates, not a requirement to hold both roles.
Choose a suitable schema
Open Reference tables and Create a reference table. Enter Table name. Use customer/product template when it matches the intended data, or Start a custom table and declare the required columns.
Each row needs a unique row_id. It identifies that retained row across later versions. Choose matching-key columns for the business identity used to find a row. A row's position in the grid is neither its row identity nor its matching key.
Use lower-case letters, digits and underscores for column names, beginning with a letter. Choose Text, Whole number or True or false. Set whether null is permitted. Use Text for exact codes such as 000127 or a customer SKU, even if today's values contain only digits.
Check identities before creation
Review every column's meaning, type, null permission and matching-key role. Two rows with distinct row_ids can still conflict if their matching key is duplicated. Empty text and null are separate values; plan which is appropriate for each field.
For a WooCommerce SKU mapping table, use the specific supported creation workflow. Its schema carries the terms the shop mapping release consumes. A generic table with a similar label does not become a shop mapping automatically.
Confirm and populate the table
Create the table and inspect the resulting table panel. If the server's answer is uncertain, inspect the recorded table identity before creating another. Do not assume a lost answer proves creation failed.
For ordinary tables, Owner OR Operator can maintain the rows. The WooCommerce SKU template requires Author. Continue with Review and save table data. The first saved version gives later exports and mappings an exact reference. If the schema choice was wrong, prepare the appropriate new table and deliberate handover rather than silently reinterpreting values under a different type.