Manage matching knowledge#
Knowledge contains the aliases, attributes, and unit conversions used to match an order to your catalog. If the same item needs correction in several orders, check the values here.
Aliases#
Link a name used by a customer to a StackCube SKU.
- Use Organization when everyone uses the same name.
- Select a customer when the name is used only by that customer.
- Do not link the same alias to different SKUs. A conflict requires the reviewer to choose the item again.
The list includes aliases learned from approved orders and aliases added by your team. Check the source and status, then edit or disable an incorrect entry.
Attributes#
Register terms that distinguish items, such as color, material, and specification. For example, warm white and soft white can point to the same color value.
Check the selected SKU and aliases before saving an attribute. Select Required constraint when the attribute must distinguish the SKU, Explicit constraint when it should apply only if the order states it, or Expression correction when only the wording needs normalization.
Unit conversions#
Add a conversion when the customer order unit differs from the catalog unit.
For example, if the catalog unit is piece and one customer box contains 20 pieces, enter box as the order unit and 20 as the factor. The selected SKU must have a catalog unit.
Upload an Excel file#
The Alias, Attribute, and Unit conversion tabs each provide an Excel template.
- Select Excel upload and download the template.
- Use the example sheet to fill in the upload sheet.
- Check the SKU, customer code, and scope.
- Upload the file and correct any missing or conflicting values.
You can upload up to 1,000 rows at a time.