What you can upload
Or skip the file entirely: paste the rows straight into the order box.
| Input | Works | Watch out for |
|---|---|---|
| Pasted text | Tab- or comma-separated rows, straight from a spreadsheet. | Nothing. This is the fastest route for a short order. |
| CSV | Comma or semicolon separated; quoted fields; decimal comma. | A number written as 1.234 is a thousand-separated 1234 in some locales and one-and-a-bit in others. Check one row after import. |
| XLSX | The first sheet, read directly in your browser. | Formulas are read as their last saved result. |
| PDF packing list | A PDF produced by software, where the text can be selected. | A scanned or photographed page has no text layer and reads as empty. Reading scans is on the roadmap; it is not built. |
Files are read in your browser. The rows reach our servers only once you save the plan.
Column headings it recognises
Case matters nowhere, and English and Turkish headings both work. This table is checked against the parser itself, so it cannot drift from what the product actually accepts.
| Role | Headings that work | Needed? |
|---|---|---|
| Product code | Code · SKU · Item No · Part No · Stok Kodu | Yes. This is how a row finds its case in the catalog. |
| Cases | Cartons · Cases · CTN · Boxes · Koli | Yes, unless you give a piece quantity and the catalog knows how many pieces are in a case. |
| Pieces | Quantity · Qty · Pcs · Units · Adet | Useful. Converted to cases when the pack size is known. |
| Description | Description · Product · Item Name · Açıklama | No, but it makes the review table readable. |
| Weight | Gross Weight · Net Weight · Weight · Ağırlık | Only with a unit — see the rule below. |
| Barcode | Barcode · EAN · UPC · GTIN | No. Kept for matching, never used in the plan. |
| Ignored on purpose | Price · Amount · Total · Volume · CBM | Commercial columns are skipped, not misread as a quantity. |
The weight-unit rule, and why it looks unhelpful
The unit is read from the heading. If the heading does not say which unit it is, the weight column is ignored on purpose.
| Heading in your file | Unit used |
|---|---|
Weight (lb) | Pounds. |
Gross Weight kg | Kilograms. |
Weight | None. The column is read as a number but not used as a weight. |
Why not just assume your company’s unit? Because a pallet plan bound to the wrong unit is worse
than a plan with no weights at all. At 3,000 lb per pallet, reading
kilograms as pounds fills a pallet that is more than twice its cap — and the plan looks perfectly
reasonable on screen. Add kg or lb to the heading and it is used immediately.
Long orders, and rows it could not place
Two things change once an order stops being short.
- Over 12 rows the table switches to a compact view with a search box, filters and a summary that stays in view while you scroll. Rows collapse; open one to see its detail.
- Rows whose code is not in the catalog are listed separately with a count. Nothing is silently dropped and nothing is guessed: a case with no dimensions cannot be planned, so you either add it to the catalog or remove the row. Your product catalog covers what it needs.
- Unreadable rows are reported with their line number and the reason — an empty code, a quantity that is not a number. The rest of the order still imports.
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.