Orders from an add-on on another ERP, brought into one order flow.

Until its migration, an add-on runs its own ERP. Its customers keep emailing POs to the same people, who key them into the old system with the old item numbers, while the platform wants every order handled one way.

The job is to read each of those POs once and draft the order the way the platform keeps it: your account, your item numbers, your units and the right branch, with the add-on's own item number shown beside each line.

Nothing is entered anywhere during the test. The drafts sit next to the orders the add-on's team actually keyed, so your reviewer checks every line against real work.

Why this job exists. Platforms in distribution grow by buying. KSM, an accounting and advisory firm, counted 75 distribution deals in the second quarter of 2026 and said add-ons drove the private equity side. Each add-on arrives with its own customers, item file and often ERP: say, an Eclipse shop joining a Prophet 21 platform.

One product, three numbers. The same product carries one item number in each system, and the customer's part number may match neither. The add-on may stock it by the each where you stock it by the box, or still carry a number you superseded years ago. The manufacturer's part number is often the only thing both files share, and even that is typed differently: with or without dashes, with a prefix, or with a pack size on the end. A line is right only when all three numbers point to one product at one unit.

Shared customers. A contractor who bought from both companies before the deal now has two account numbers, two ship-to lists and two sets of contract prices. Which account an order lands on, and which price holds, is a decision your team has probably made but rarely written down. In this test it goes into the success criteria before any draft is judged.

The add-on still ships it. Branch codes, tax setup and freight terms differ between the two companies. A will-call order is still picked at the add-on's counter, and a drop-ship line still goes to the add-on's vendor until purchasing is combined. So each draft keeps the add-on's fulfillment details, even when the item and account are in your terms.

Who reviews. The best reviewer knows both catalogs: often the add-on's longest-serving inside salesperson, working with the platform's integration lead. On each line they check that the draft says what the add-on's team keyed, and that the add-on's item maps to the right one of yours. Every confirmed match can carry into your cross-reference or migration file.

When your reviewer says yes against the success criteria, the same job runs on the add-on's incoming POs for about 30 days.

A person approves every draft before it posts to the ERP that ships it. How an approved order gets there, whether keyed, imported from a file or sent through a connection you already have, is agreed and priced before you sign.

The item matches your reviewer confirms carry forward. When the add-on moves onto your ERP, those lines are already checked.