Import an order from a design file with the Importer

Your customers send orders in whatever format they already use, and retyping those into Allmoxy costs you hours you'll never bill for. The Importer reads the file as it is, uses AI to match each line to a product in your catalog and each detail to its attributes, and shows you the matches to confirm before it creates the order. If something goes wrong, see My import failed, is stuck, or won't let me continue.

Applies to: employees on catalog shops with the Importer turned on, at Orders > Importer. It is for your team, not your customers: they won't see it in their ordering portal and keep ordering the way they do today. If you don't see Importer in the Orders menu, ask your Customer Success Manager.

In this article

What you can bring in
Before you start
Upload your files
Match your product names
Match your attribute names
Create the order and check it
Finish an import later
It learns your matches
Things to know

What you can bring in

The Importer reads these file types, with a size limit per type:

.ordx, a Cabinet Vision order export: 10 MB.
.zip, a Mozaik job folder zipped as it is: 25 MB.
.xml or .txt design software exports: 10 MB.
.pdf, a printed quote: about 4.5 MB.
.jpg, .jpeg, .png or .webp, a photo of a handwritten or printed order: about 3.75 MB.

You can drop several files at once; each becomes its own import with its own matching steps. Two things worth knowing up front:

CSV isn't on the list. The original Import Order tool only accepts CSV files built to your catalog's template; if it is working for you, stay there, at Orders > Import Order (Legacy). See Import an order from a CSV file (Import Order Legacy).
Photos are new and still improving. You can photograph a handwritten or printed order and the Importer will read it; some come through beautifully, some don't yet. Photos work best sharp and straight on: worth trying, not something to build your workflow around just yet.

Before you start

There is nothing to set up. Who sees it: employees on a catalog shop (not project-only) with the Importer turned on, signed in through Allmoxy's standard sign-in and not set to Deny on the Use Import Tool permission. Customers never see it.

It brings in product information only: products, quantities, sizes and attributes. It doesn't assign the customer, shipping or other order details; you set those on the order at the end, as with the legacy CSV importer.

Clean product names pay off. The AI matches the file against your catalog names, so the more consistent your naming, the more matches land in the high-confidence group and the less clicking you do. A messy catalog still works; you'll just confirm more by hand the first time.

Upload your files

Go to Orders > Importer (NEW badge, just above Import Order (Legacy)).
The Import Tool page opens on the Upload files step. Drag your files onto the drop zone, or click Browse files.
Click Start Import. Each file uploads with its own progress ring and can be canceled while uploading.
Each file appears at the top of the Previous imports table while Allmoxy reads it. The page does not move on by itself; the table refreshes every 10 seconds until every row has settled.
When a row's Status says Awaiting product mapping, click Continue on that row.

The table's columns are Task, File name, Type, Status, Order and Actions; you can search it and filter by Created and Updated date ranges. Once an order exists, its number in the Order column opens it in a new tab.

Match your product names

This is where you check the AI's work, and it goes faster than it looks. The screen lists every product name in your file, grouped by how confident the Importer is about each match:

High Confidence Match: near-certain. Usually you can scan these and move on.
Medium Confidence Match: probably right, worth a look.
Low Confidence Match: the AI's best guess. Check each one.
No Match: nothing in your catalog was close enough. These rows start empty and must be mapped or skipped.

Nothing is pre-confirmed, even in High. Each row shows the original imported name, a Count, and the catalog product it maps to. Lines with the same name are combined, so Count is the total quantity coming in: a count of 8 might be eight identical pieces or eight sizes of the same product. Either way, confirming the row once covers all of them.

From here you can:

Confirm a row to accept the match.
Confirm all at the top of a group to accept every remaining row that has a match: the real time-saver on your high-confidence group.
Click Maps to if a match is wrong: search for the right product or browse by category, and picking one confirms the row.
Switch on Skip this one in that browser if you don't want the product on the order. Clicking Skipped puts it back.

One thing to be clear about: a skipped product doesn't get imported. It won't come in blank for you to fix later; it simply won't be on the order. If you want it there, map it, even if its attributes don't fully map.

The counter at the bottom tracks what's left. Once every line is confirmed or skipped, Continue to Match attribute names becomes available; it sends your product choices and a "Matching your attributes" box shows progress.

Match your attribute names

Your products are sorted. Now make sure their details came through too. Attributes are the specifics: width, height, depth, edge banding, back material, hinge drilling. The Importer takes whatever the file called them and matches each to the attribute in your catalog.

The rows work the same way, with more context. One row is one file attribute for one product, so you see the catalog product name and the attribute type (Group, one value for every line of that product, or Line Item, a value per line, with a count) beside the imported name. That matters: two different products can each have a "Width" that isn't the same attribute. The browser only offers that product's attributes, so you can't cross them by accident.

Confirm, Confirm all, re-map or skip, the same as before, with three extra details:

When the catalog attribute is a fixed list, an Attribute option field appears under Maps to. If the file's value matches an option exactly it is filled in for you; otherwise the field shows a red edge and you pick the option before the row can be confirmed.
A number attribute can't take a value that isn't a number ("3/4 White Melamine" on a width). The row says why, and Confirm opens the browser to choose a different attribute.
Two file attributes on one product mapped to the same catalog attribute show a Duplicate mapping tag. It is a warning only; the order can still be created.

Confirm all is offered on the High and Medium groups here. Skipping an attribute behaves differently from skipping a product: the product still comes in without that attribute selected, and you can fill it in on the order afterward.

Create the order and check it

Once every attribute row is confirmed or skipped, click Create Order.
A "Creating your order" box shows progress. From 15 seconds in it offers Leave and keep importing, which returns you to the table while the work continues.
When the order exists, you are back on the Import Tool page with the message "Successfully imported. See import #N, and order #M." Both numbers are links that open in a new tab, and the message closes after 12 seconds. (If nothing needed attribute review, you return without it; the order number is in the Order column.)
Open the order and do two things before you send it anywhere: set the customer (the Importer doesn't assign one) by choosing the company on the order; then scan the line items, check sizes and quantities, and fill in any attributes you skipped.

From there it's a normal Allmoxy order: price it, send it, produce it.

Finish an import later

You don't have to finish an import in one sitting, which helps when a big file deserves a real review. Each lives in the Previous imports table, with search and date ranges for finding older ones. The Status column tells you where each stands:

Processing or In progress: Allmoxy is reading the file. Wait; the table refreshes on its own.
Awaiting product mapping: ready for the product step. Click Continue.
Awaiting attribute mapping: the attribute step is next. Click Continue.
Processing with attribute mappings: the order is being built. No button; wait.
Completed: the order exists; the Order column links to it, and View opens the import read-only.
Failed: the import stopped. Today the row shows no reason and has no retry; see My import failed, is stuck, or won't let me continue.

One catch: product choices are kept once you press Continue, but attribute choices are not saved between visits. Reloading or leaving the attribute step starts it again from the AI's suggestions, so finish it in one go. Going back to the product step after sending it doesn't resend anything: changes there are ignored.

It learns your matches

The Importer remembers the matches you confirm. Import from the same customer next month and more should land in High Confidence Match, so you're confirming a group instead of working down a list. It gets lighter over time, not heavier.

Things to know

Each shop has a monthly AI allowance, shared with Operator. When it is used up, a banner says imports are paused and new uploads fail until next month; an import already running finishes. Ask support@allmoxy.com if you run out early. See Guide: Operator.
Your attribute choices are not saved between visits. Product choices are kept once sent; the attribute step starts over on a reload.
A skipped product is left off the order entirely. Map it if you want it there, even with incomplete attributes.
CSV files still go through Import Order (Legacy), including a Cabinet Vision cut list; the Importer takes the ORDX.
The size limits are firm. A 6 MB ORDX or a 20 MB Mozaik zip is fine; a 6 MB PDF or a 4 MB phone photo is refused, so re-save it smaller.
Leaving the page while files are uploading asks you first, so you don't lose an upload by accident.