StackCubeDocs
Documentation

Build the item catalog#

You do not need to import every item before connecting a channel. Start with the items that fail to match in the first real order.

StackCube item catalog
Item code, SKU, name, unit, and sales price in Item management.

Choose a registration method#

Catalog situationMethod
You need only a few items for the first orderAdd them directly in Item management
You manage items in a CSV or spreadsheetUpload a CSV or XLSX file
Items are already maintained in EcountSync the ERP catalog

See Bulk item management for larger imports.

Enter the first fields#

FieldWhat to enter
Item code or SKUThe code your company uses to identify the item
Item nameThe standard name shown during order review
Specification and unitThe rule for interpreting boxes, pieces, kilograms, or other quantities
StatusKeep items used in new orders active
Default sales priceThe price used when no customer-specific rule applies

For order portal items, also check the image, description, options, and portal visibility.

Add aliases#

Add an alias when a customer uses a different name from the catalog.

For example, if the standard name is Americano Beans 1 kg but an order says Americano beans or beans 1 kilo, save those terms as aliases.

Use aliases for repeated abbreviations, former names, customer-specific terms, and common typos. Avoid adding every one-off phrase because broad aliases can create incorrect matches.

Separate options and pack sizes#

Create a separate option or SKU when color, size, volume, or pack size changes what fulfillment ships. Do not keep a fulfillment-critical difference only in a note.

If 1 box, 12 pieces, and 1 piece represent different quantities, agree on unit and conversion rules with the order review team.

Add customer-specific prices#

Enter a default sales price first. Add a price tier or rule only for customers that use a different price. See Customer-specific pricing.

Return to the first order#

After adding the item, return to the first order and check:

  1. The customer term matches the new item.
  2. Quantity and unit are correct.
  3. The default or customer-specific price is applied.
  4. Required review warnings are resolved.

When the same correction appears in several orders, update the item or alias instead of editing every order line.