The six fields a case cannot be planned without
These are required because the plan is arithmetic, not a guess. A missing dimension cannot be estimated from a product name.
| Field | CSV heading | What it decides |
|---|---|---|
| Product code | sku | How an order row finds this case. Unique inside your company. |
| Pieces per case | case_pack | Turns a piece quantity on the order into a number of cases. |
| Case length | length | Layer geometry and rotation. |
| Case width | width | Layer geometry and overhang. |
| Case height | height | How many layers fit under the height cap. |
| Case weight | weight | The pallet weight cap and the heavy-on-the-bottom order. |
The optional fields, and which one actually matters
Three optional columns. One of them changes plans more than anything else you can type.
| Field | CSV heading | Effect when you fill it in |
|---|---|---|
| Max load on top | max_load_on_top | The one that matters. The weight this case can carry. Without it the planner falls back on a rule of thumb; with it, crushing becomes arithmetic instead of judgement. |
| Stackable | stackable | Set it to false and nothing is ever planned on top of this case. |
| This side up | this_side_up | Blocks rotations that would lay the case down. |
| Name | name | Only for reading. It never changes a plan. |
Any heading Tiercube does not recognise is skipped rather than misread, so exporting
extra columns from your ERP is harmless. Common variants of these names work too — code,
case_weight, units_per_case, and the Turkish equivalents.
Units, and the limits a value has to stay inside
Numbers are read in your company’s measure system unless the heading says otherwise. Write
length (cm) or weight kg and that column is read in those units, whatever the
company setting is.
| Value | Upper limit | Why there is a limit at all |
|---|---|---|
| Any case dimension | 120 in (305 cm) | A “case” 400 in long is almost always centimetres typed into an inches column. |
| Case weight | 2,000 lb (907 kg) | Same mistake in the other direction: kilograms read as pounds. |
| Pieces per case | 100,000 | Catches a barcode pasted into the pack-size column. |
Rejected rows are reported with their line number and the reason. The rest of the file still imports, so a single bad row does not cost you the upload. Up to 5,000 products per file.
Retiring a product
Catalog entries are deactivated, not deleted.
- A deactivated case disappears from search and from new orders, and its code stops matching.
- Plans you already saved keep their own copy of the numbers, so an old plan still reads correctly years later even if the case has changed shape since.
- This is deliberate: deleting a case would silently rewrite the history of every plan that used it.
Still stuck?
Email us and describe what you expected to happen. Include the order file if you can — most questions are answered fastest by looking at the actual rows.
hello@themorfose.com Back to the help center
We do not publish a response-time target yet, so we are not promising one. There is no phone line and no chat — email is the only support channel today.