Skip to main content

Packaging Levels

Packaging levels describe how a product is packaged. They help customers understand what they are ordering and how many units are inside a larger package.

What they are

A packaging level is one layer of a product package. Examples:
ProductStructure
Crate of bottlesCrate → Bottle
Box of tomatoesBox → kg
Carton of cansCarton → Can
Bag of flourBag → kg
These structures make product quantities clearer.

Why they matter

Customers often order one large package, but the product may contain smaller units. Example:
Ordered unitContains
1 crate12 bottles
1 box10 kg
1 carton24 cans
This helps avoid misunderstandings between vendor and customer.

Typical structure

A product can have one or more levels.
LevelMeaning
Top levelMain package the customer orders
Inner levelSmaller unit inside the main package
Unit levelBase unit such as kg, L, piece, bottle, or can
Example:
LevelNameMeaning
1CrateCustomer orders one crate
2BottleOne crate contains bottles

Example: Crate with bottles

A vendor sells water as a crate with 12 bottles.
LevelQuantity
Crate1
Bottle12
The customer sees that one ordered crate contains bottles.

Example: Bag with weight

A vendor sells flour as a 25 kg bag.
LevelQuantity
Bag1
kg25
This is useful when the product is ordered as a bag, but the content is measured in kilograms.

Manual setup

Vendors can define the structure manually. Manual setup is useful when:
  • The product packaging is special
  • The automatic result is not correct
  • The product has several package layers
  • The package contains a fixed number of units
  • The product should be shown more clearly to customers

AI packaging

Mathership can also try to create the structure automatically from the packaging text. Example packaging text:
Crate with 12 bottles
Mathership may detect:
LevelQuantity
Crate1
Bottle12
AI packaging can help create packaging levels faster, but vendors should review the result.

Fields

Packaging setup can include information such as:
FieldMeaning
NameName of the level
Quantity per parentHow many units are inside the parent level
OrderPosition of the level
Unit codeOptional unit such as kg, L, piece, or bottle
The exact fields shown can depend on the user interface.

Quantity per parent

Quantity per parent describes how many smaller units belong to the level above. Example:
Parent levelChild levelQuantity per parent
CrateBottle12
Boxkg10
CartonCan24
This means one parent package contains the given number of child units.

Order of levels

The order defines the hierarchy. The top level normally has the first position. Example:
OrderLevel
0Crate
1Bottle
This means the product is ordered as a crate, and bottles are inside the crate.

When to use them

Use packaging levels when:
  • Customers need to understand package contents
  • Products are sold in crates, boxes, cartons, bags, or cases
  • A package contains smaller units
  • The product should later be mapped to inventory
  • Order exports should include clearer packaging information

In orders

When customers order products, the structure helps explain what the ordered quantity means. Example:
Customer ordersMeaning
2 crates2 main packages
2 crates with 12 bottles each24 bottles total
This can reduce errors during order processing.

Bulk uploads

Bulk uploads can include packaging text. After upload, package details can be added manually or generated with AI packaging. This allows vendors to upload products first and refine packaging details later.

Inventory mapping

Packaging levels can support product-to-ingredient mapping. Example:
Vendor productPackage contentInternal ingredient
1 box tomatoes10 kgTomatoes
1 crate milk bottles12 bottlesMilk
This helps convert vendor products into internal stock units.

Typical workflow

  1. Open your vendor company
  2. Go to Products
  3. Open a product
  4. Review the packaging text
  5. Add or update the package structure
  6. Save the product
  7. Check how the product appears to customers

Example: Add levels manually

StepAction
1Open the product
2Add top level, such as crate or box
3Add inner level, such as bottle or kg
4Enter the quantity per parent
5Save the setup

Example: Use AI first, then review

StepAction
1Open the product
2Run AI packaging
3Review the detected levels
4Correct names or quantities if needed
5Save the final setup

Common problems

Structure looks wrong

Check that:
  • The level names are correct
  • The quantity per parent is correct
  • The order of levels is correct
  • The packaging text is not misleading

Customer does not understand the product

Add clearer package details or improve the product packaging text. Example:
UnclearClearer
BoxBox, 10 kg
CrateCrate, 12 bottles

AI created the wrong result

Edit the levels manually. AI results should be reviewed before relying on them.

Quantity is unclear

Check whether the quantity describes:
  • The number of ordered packages
  • The number of units inside a package
  • A weight or volume
  • A piece count

Best practices

Keep names simple

Use names customers understand, such as crate, box, bottle, can, bag, kg, or L.

Use consistent units

Avoid mixing different unit names for the same meaning. Example:
Less consistentMore consistent
kilogram, kilo, kgkg
liter, litre, LL

Review AI results

AI packaging can save time, but it should not replace a final vendor check.

Match real ordering

The top level should match what the customer actually orders.

Keep product text and structure aligned

If the product says “crate with 12 bottles”, the levels should show the same structure.

AI Packaging

Generate packaging levels from product packaging text.

Adding Products

Add new products to the vendor catalog.

Edit Products

Update product names, prices, stock, packaging, and images.

Bulk Product Upload

Upload or update many products at once.

Product Images

Manage product images and image sources.

Product Mapping

Connect vendor products to internal ingredients.
Last modified on May 8, 2026