Configuring Export Files for Nesting Software
Here's how to give our Implementation Engineers exactly what they need to build the perfect export for your workflow.
Allmoxy can generate custom export files that integrate seamlessly with your nesting software, CNC machines, and other manufacturing systems. Since every system has its own requirements and every customer has unique product definitions, these exports need to be configured specifically for your setup.
Here's how to give our Implementation Engineers exactly what they need to build the perfect export for your workflow.
Why Your Product Definitions Matter (A Lot!)
Before we dive into the technical steps, here's something crucial to understand: How your products are defined in your nesting software might impact how your Allmoxy catalog is structured.
Think of it this way - if your nesting software expects products to be organized or named in a specific format, we want to make sure your Allmoxy setup aligns with that from the start. This prevents headaches down the road and ensures your export files work flawlessly with your existing processes.
The Magic Formula: Work Backwards from Your Nesting Software
Getting two separate systems to talk to eachother is always an iterative process.The easiest and most accurate way to configure your export is to let your nesting software show us exactly what it needs. Here's our suggestion for getting the right data from Allmoxy to another system:
Step 1: Create a Typical Order in Your Nesting Software
Open up your nesting software (Cabinet Vision, Mozaik, Microvellum, CutRite, or whatever system you use) and create a representative order. Make it realistic - include the types of products, configurations, and details you'd normally process.
Don't overthink this step. Just build an order that looks like what you'd typically send to production.
If you're building a new line in Allmoxy that you don't currently produce through this system, consult with an Implementation Engineer.
Step 2: Export That Order
Once your sample order is complete, export it using your software's standard export function. Most nesting software can export in several formats, and we can work with:
- .ord files (we support .ord but not .ordx file types currently)
- .xml files
- .csv files
Choose whichever format your software exports most naturally - there's no "best" option from our perspective.
Step 3: Send It Our Way
That's it! Our Implementation Engineers can read all these file types and work backwards to understand exactly what structure, data fields, and formatting Allmoxy needs to provide in your custom export file.
Why This Method Works So Well
By starting with your nesting software's output, we eliminate guesswork. Instead of trying to anticipate what your system needs, we can see exactly:
- What data fields are required
- How products should be formatted and named
- What order information needs to be included
- How measurements, materials, and specifications should be structured
This reverse-engineering approach means your Allmoxy exports will integrate perfectly with your existing workflow from day one.
Ready to set up your export? Create that sample order in your nesting software, export it in your preferred format, and send it to your Implementation Engineer. They'll take care of the rest and have you up and running with seamless data integration in no time.
It's important to note that building exports is an iterative process. Our Implementation Engineers don't always have access to the systems you're using, so we need your participation in testing and verifying that the data is accurate!