Build your item catalog#
The item catalog is the reference StackCube uses when AI turns raw order text into matched order lines. A clean catalog reduces review time and prevents shipment errors.
Required fields#
Start with these fields for each item:
| Field | Purpose |
|---|---|
| SKU | Stable internal item identifier |
| Name | Standard item name used by your team |
| Option | Size, color, package, unit, or variant |
| Status | Active, inactive, discontinued |
| Default price | Price used when no customer price tier rule applies |
Aliases#
Customers rarely order with your exact catalog name. Add aliases for names that appear in email, KakaoTalk, Excel files, PDFs, and portal notes.
Good aliases include abbreviations, old product names, buyer shorthand, unit names, and common typos.
Options and variants#
If item option mistakes create fulfillment problems, model options explicitly. Do not hide important shipping or packing differences inside free text.
Examples:
- Same product, different package size
- Same apparel item, different color and size
- Same component, different specification
- Same food item, frozen versus chilled
Pricing#
Set a default price first, then add customer price tiers and tier rules only where they matter. StackCube can help reviewers compare submitted prices with the configured item or tier price.
Use customer pricing when customer groups need negotiated fixed prices, tier discounts, or date-limited rules.
Bulk Setup and Maintenance#
For large catalogs, use CSV upload, existing-item update upload, bulk image upload, and selected-row bulk edits in Item management. Bulk tools are safer than manual entry for initial migration and portal readiness.
See bulk item management for the detailed workflow.
Catalog maintenance#
Review aliases after the first week of live operation. Every correction in the review queue is a signal that the catalog can be improved.