What Belongs on a Go-Live Checklist for an Apparel ERP

It is the Thursday before a Monday cutover. The implementation team is on a call with the brand’s ops director, the warehouse manager, and the controller. Someone asks whether the opening inventory snapshot has been reconciled against the 3PL’s last cycle count. Silence. Someone else asks whether the EDI 856 templates have been tested with the top three retailers. Silence. The project plan says ninety-four percent complete. The brand goes live on Monday anyway. By Wednesday, allocation is broken, two wholesale orders have shipped against DTC-committed inventory, and the controller cannot tie the opening balance to anything. None of this was on the checklist, because the checklist was a Gantt chart.

What is an apparel ERP go live checklist, really?

An apparel ERP go live checklist is the set of operational conditions that must be true on cutover day for the business to keep running without manual rescue. It is not a list of tasks the implementation team has completed. It is a list of outcomes the operations team can verify. The distinction matters because tasks can be ninety-four percent done while the outcomes they were supposed to produce are still broken.

The pattern across the implementations my team has shipped is that the brands who go live cleanly treat the checklist as a readiness contract between implementation and operations. Each item is phrased as a statement of fact that someone on the customer side has to confirm. Opening inventory matches the 3PL within a defined tolerance. The top five retailer EDI maps pass a 997 acknowledgement in test. The chart of accounts in the ERP ties to the chart of accounts in the GL one-to-one. If any of those statements is not yet true, you do not go live. You move the date.

When I sit in on a customer kickoff, the question I ask first is who owns each of those statements on the customer side. Not who owns the task. Who owns the truth. If the answer is the implementation consultant, the project will stall in the first ninety days because the brand has not internalized what they are taking responsibility for.

Why do most go live checklists fail?

Most checklists fail because they are written by the implementation partner for the implementation partner. They track configuration steps. Did we load the size scales. Did we set up the warehouses. Did we map the customers. Those are necessary but they are not sufficient. A correctly loaded size scale does not tell you whether the brand can release a purchase order. A configured warehouse does not tell you whether the WMS will accept an ASN.

The second failure mode is treating data migration as a one-shot event. Apparel brands have living data. Styles are added weekly during development cycles. Costs change as factories quote. Inventory moves every hour. A migration that was clean two weeks before cutover is dirty on cutover day. The checklist needs a freshness clause for every data domain, with a defined cutoff and a reconciliation step after the cutoff.

The third failure is omitting the finance close. This is where the sixth breakpoint of the 6 Breakpoints framework lives. Reporting becomes reactive when the operational system and the GL do not agree on opening balances, in-transit inventory valuation, or revenue recognition timing. Most go lives skip the finance reconciliation because it feels like a post-launch concern. It is not. If finance cannot close month one cleanly, the brand spends the next two quarters in political reporting instead of operational reporting.

What belongs in the product data section?

Product data is where most apparel implementations either succeed or fail quietly. The checklist items here are about completeness and authority, not just presence.

Every active style has a complete bill of materials with current costs. Every active style has size and color attributes that match what the WMS expects on inbound receipts. Every style has a status that reflects whether it can be sold, only pre-ordered, or is in development. Discontinued styles are flagged so they do not appear in B2B catalogs.

The authority question matters more than the completeness question. Who owns the style master after go live. If the answer is two teams, you have not finished the implementation. Design owns the style during development. Production owns it through the first PO. Merchandising owns it once it is available to sell. Each handoff has to be defined or styles will sit in limbo and orders will be written against records that do not have costs, weights, or country of origin codes.

For brands with international wholesale, country of origin and HS codes belong on the checklist as a blocking item, not a nice-to-have. Magnolia Pearl learned this the hard way when international duties became unmanageable without that data living on the style record. If the customs broker is calling the warehouse for HS codes, the data architecture has failed.

What belongs in the inventory section?

The inventory section is the most operationally dangerous part of the checklist because errors here cascade into every other module. Allocation logic depends on inventory truth. Wholesale commitments depend on allocation. EDI fulfillment depends on commitments. Chargebacks depend on EDI fulfillment.

Opening inventory must be reconciled to the 3PL or in-house WMS within a tolerance defined in writing. For most brands, that tolerance is zero on the SKU count and within one percent on units. Not within five percent. Not within ten percent. If the number is off by more than one percent on day one, the system will be wrong every day after, and the ops team will spend six to nine hours a week reconciling Shopify, the 3PL, and wholesale, which is exactly the pattern we see at the $15M revenue band for brands running wholesale plus DTC plus 3PL.

In-transit inventory needs a defined treatment. Goods on the water from the factory are inventory the brand owns but cannot ship from. The checklist needs to confirm that in-transit POs are loaded, expected arrival dates are current, and the planning team knows how to distinguish on-hand from on-order in every report they look at. Channel-aware ATS depends on this. If your ATS shows in-transit as available, you will oversell at peak. Two to three percent oversell is the typical pattern for brands who go live without this guardrail.

Returns deserve their own line. Returns should post to inventory in days, not weeks. The checklist should confirm that the return-to-stock workflow is tested end to end, from the customer’s RA through the 3PL inspection through the inventory adjustment. If returns sit in a holding bucket for three weeks, your sellable inventory is understated and you will say no to orders you could have filled.

What belongs in the order and channel section?

Wholesale and DTC have different failure modes and the checklist has to treat them separately. Wholesale should not run through Shopify’s native flow. If the implementation has not stood up a proper B2B order capture path, with credit limits, terms, ship windows, cancel dates, and allocation against wholesale-committed pools, then the brand is not ready to go live on wholesale.

For wholesale, the checklist needs to confirm that the top retailers are mapped. EDI 850 inbound, 855 acknowledgement, 856 ASN, 810 invoice, 846 inventory advice where required. The maps need to be tested in the trading partner’s test environment, not just internally. A 997 acknowledgement in your own sandbox is not proof that Nordstrom will accept your ASN. If chargebacks exceed one percent of wholesale revenue in the first quarter after go live, the EDI integration is the problem, not the warehouse. That diagnosis is worth writing down before cutover so the team knows where to look when the chargeback reports start coming in.

Lufema’s multi-entity wholesale setup is a useful reference for brands carrying more than one brand or operating in more than one country. Each entity needs its own customer master, its own price list, its own credit decisions, and its own B2B portal experience. A single shared catalog will not survive contact with reality. The checklist should confirm that entity separation is enforced at the data layer, not just the UI layer.

For DTC, the checklist is shorter but the timing is stricter. Order import from Shopify needs to clear within minutes, not hours. Returns need to flow back. Fraud holds need to route to a queue that someone watches. Drop launches need an inventory reserve workflow if the brand runs drops. Magnolia Pearl’s same-day fulfillment pattern only works if the order routing is tested under load before the first real drop. Going live two weeks before a drop is going live during the drop.

What belongs in the warehouse and 3PL section?

The warehouse is where the fifth breakpoint lives and where the 3PL blind spot does the most damage. The checklist here has to confirm that the integration is bidirectional, real-time enough for the business, and reconcilable.

Inbound POs flow to the 3PL with expected receipt dates. Receipts flow back with discrepancies flagged. Outbound orders flow to the 3PL with priority and ship-by dates. Shipment confirmations flow back with tracking numbers and actual ship dates. Inventory adjustments from cycle counts flow back daily, not weekly. If the 3PL only sends a flat file once a day, the brand will be running blind for twenty-three hours out of every twenty-four. That is acceptable for some businesses and unacceptable for others. The checklist needs to make the decision explicit.

ASN timing is its own checklist item. The retailer’s compliance manual will specify when the 856 must be sent relative to the physical shipment. EDI 856 sent within two hours of pick is a common standard. The checklist should confirm that the 3PL’s pick confirmation triggers the ASN automatically, not on a batch overnight job that misses the window.

What belongs in the finance and reporting section?

Finance is the section most often deferred and most often regretted. The checklist needs four things to be true before cutover.

Opening balances tie. Inventory on hand in the ERP equals inventory on hand in the GL on the conversion date. In-transit valuation is loaded and matches the open PO ledger. The chart of accounts is mapped one to one so that every transaction the ERP generates posts to a real GL account, not to a suspense bucket. Revenue recognition rules are configured for wholesale ship-complete versus partial ship behavior, because those drive different timing.

The reporting layer needs at least one weekly operational report that the leadership team agrees to read in the first month. Sell-through by style and channel, inventory by location and status, open orders by ship window, chargebacks by retailer and reason code. If the brand goes live without a defined operational reporting cadence, reporting becomes political within sixty days. People will pull their own numbers and the numbers will not agree. Run OTB weekly during selling season, monthly is too slow, and the checklist should confirm the OTB report is built and validated before cutover, not after.

When is a brand actually ready to go live?

A brand is ready to go live when every statement on the checklist can be answered yes by someone on the customer side, in their own words, without the implementation partner prompting them. That is the only test that matters. If the ops director cannot describe how a wholesale order with a partial backorder will flow through allocation, picking, ASN, and invoicing, then the team is not ready, regardless of what the project plan says.

Readiness is also about people, not just systems. Who is the first-line owner for each module after go live. Who escalates to whom. What is the SLA for fixing a broken EDI map. What is the daily standup cadence in the first two weeks. Brands in the $10M to $20M range typically replace three to five tools plus spreadsheets when they consolidate onto a unified apparel operations platform, and the human reorganization that comes with that is bigger than the system change. The checklist should name the new owners explicitly.

What this means for an apparel operations team

The go live checklist is the document that decides whether the next ninety days are spent operating or rescuing. A weak checklist gets you to a launch date. A strong checklist gets you to a launch that holds. The difference is whether each item is a task someone did or a truth someone confirmed.

The operational discipline that produces a clean checklist is the same discipline that produces a clean close, a clean allocation run, and a clean chargeback report six months later. It is worth slowing the timeline by two weeks to get the readiness contract right. The brands who do that recover the two weeks within the first month of operations. The brands who do not spend the next two quarters reconciling.

If the checklist for your upcoming cutover is a project plan rather than a readiness contract, rewrite it. Phrase every item as a statement of fact that an operator on your side has to sign off on. The items that no one is willing to sign are the items that will break in week one.