New Distribution Center Startup: A 120-Day Go-Live Checklist

The landlord hands over the keys, the racking contractor signs off, and the launch date has already been promised to the largest customer. Three weeks later the site is shipping 60 per cent of plan: location labels scan to the wrong aisle, half the new hires are waiting for lift truck evaluations, and the fire marshal has not yet seen the storage layout. Every one of those problems was knowable in month one.

A distribution center startup goes live on time when every workstream is tied to a dated gate, a named owner and an evidence pack that someone outside the workstream can check. Counting back 120 days from the first live order gives four 30-day gates, each with its own exit test, followed by an eight-week ramp curve that steps volume up only when accuracy and service hold at the previous step.

• What the plan covers: permits and occupancy, racking and equipment commissioning, hiring and operator training, WMS configuration and testing, the opening stock transfer, and the ramp from first order to full volume.
• Tools included: a gate calendar, a ramp-cost calculation in dollars and rupees, a labour formula, a timed launch-week failure trace, and a go or no-go checklist with pass rules.

Counting back from the first live order: four 30-day gates

Fix the first live customer order as Day 0 and plan everything backwards from it. Gate dates, not task lists, are what a steering group can hold people to.

Most launches slip because the plan is built forwards from the lease date and the go-live is whatever remains. Building backwards exposes the long-lead items at once: an occupancy inspection that a city schedules three weeks out, a printer order with a six-week lead time, a lift truck delivery that needs charging infrastructure before it can be used. Each gate below closes only when its evidence is filed.

Before any of this, the building and its layout must already be settled. Our article on the warehouse design process covers order profiling, storage media and dock sizing; this checklist assumes that design is approved and turns it into a dated launch.

Occupancy, storage permits and registrations that set the earliest date

Approvals from authorities are the only workstream you cannot accelerate with overtime, so file them at Gate 1 and treat their expected dates as fixed constraints on Day 0.

In the United States the certificate of occupancy and fire approvals are local. Where a jurisdiction has adopted the 2021 International Fire Code, Section 3201.2 requires a permit for high-piled combustible storage as set out in Sections 105.5 and 105.6; the chapter's user note applies the chapter to storage above 12 feet, or 6 feet for high-hazard commodities. Section 3201.3 lists the construction documents the permit submittal needs, from usable storage height to flue spaces.

• Posted storage layout: IFC 2021 Section 3201.3.2 requires a legible floor plan mounted on a wall in an approved location, showing rack layout, storage heights, commodity types and sprinkler clearances; print it before the inspection, not after.
• Edition check: Jurisdictions adopt different IFC editions and local amendments, so confirm with the fire code official which edition and permit form apply to your address.
• Indian GST registration: A new site in a state where the company already holds a registration is added as an additional place of business through FORM GST REG-14 within fifteen days of the change, under CGST Rule 19(1).
• New state in India: CGST Section 25(1) requires a separate registration in every state where the business becomes liable, applied for within thirty days of becoming liable, so a first site in a new state needs a fresh GSTIN.
• State approvals in India: Fire service clearance, trade licences and labour registrations are set by each state and city; list them with the local consultant at Gate 1 rather than assuming another state's checklist applies.

New distribution center startups in IFC jurisdictions need the high-piled storage permit required by 2021 International Fire Code Section 3201.2 for storage above 12 feet, and Section 3201.3.2 requires the approved layout posted on a wall, so the fire review should be filed by Day minus 120.

Commissioning racking, docks and lift trucks before people arrive

Commission every piece of fixed and mobile equipment to a signed test sheet during Gate 2, while the floor is still empty. Fault-finding with live freight in the aisles costs several times more and puts new staff at risk.

• Rack sign-off: The installer's completion certificate, load signs on every bay type, anchors and column guards checked against the drawing, and a walk-through by the person who will own rack inspections.
• Dock equipment tests: Levellers, vehicle restraints, seals, lights and door controls, each operated under a loaded trailer rather than an empty dock.
• Charging room readiness: Ventilation, eyewash and charger circuits installed and tested before the first lift truck is delivered.

In the United States, a lift truck operator may drive only after training and evaluation. OSHA 29 CFR 1910.178(l)(1)(ii) requires training to be complete before operation except during supervised training, (l)(2)(ii) combines formal instruction, practical training and a workplace evaluation, and (l)(6) requires the employer to certify each operator with names, dates and the trainer's identity. Evaluations repeat at least every three years under (l)(4)(iii).

For Indian sites we found no single national certification rule for warehouse lift truck operators comparable to the OSHA paragraph above; the practical standard is the manufacturer's operator training plus the company's own documented assessment, filed in the same way.

Hiring waves and training hours mapped to the ramp

Hire in waves timed to the ramp, not all at once. Supervisors arrive first, then trainers and the first operating wave, then later waves just before each volume step, so nobody is paid for weeks with nothing to do.

A common pattern is supervisors and leads at Day minus 75, a first operating wave of about a third of steady-state headcount at Day minus 21, and further waves a week before each ramp step. The first wave learns the building with the launch team, picks up the mock days and later trains the next wave on the floor, which is cheaper and more credible than trainers flown in for every class.

Headcount for a ramp week (direct labour, one function)

  H = V / (S × p × h × a)

  V = planned lines (or units) per day in that week
  S = engineered standard rate at steady state, lines per productive hour
  p = ramp productivity factor for that week (0.50, 0.70, 0.85, 0.95, 1.00)
  h = paid hours per person per day (for example 8.0)
  a = share of paid hours that are productive (for example 0.85)

Example, ramp weeks 1-2 in the US case below:
  V = 7,500 lines, S = 60, p = 0.50, h = 8.0, a = 0.85
  H = 7,500 / (60 × 0.50 × 8.0 × 0.85) = 7,500 / 204 = 36.8, round up to 37 pickers

Excess ramp hours per day = (V / S) × (1/p − 1)

• Employment eligibility in the US: Under 8 CFR 274a.2(b)(1)(i)(A) a new hire completes Section 1 of Form I-9 at the time of hire, and under (b)(1)(ii)(B) the employer completes Section 2 within three business days, so plan document checks into the first day of each wave.
• Agency labour in India: Where a contractor supplies the workforce, the site's admission, induction and badge process must be ready before the first wave; our guide to contractor onboarding before a warehouse shift covers that gate.
• Trainer ratio: Plan one floor trainer per six to eight new operators in the first two ramp weeks, and record each trainee's sign-off by process, not just attendance.

WMS configuration, location labels and interface testing

The warehouse system must be proven against this building's own locations, printers and network before Gate 3 closes. A configuration copied from another site is a starting point, not a test result.

Freeze the location naming standard at Gate 1, because labels, slotting files, pick paths and replenishment rules all depend on it. Load the location master from the approved rack drawing, print labels in batches by aisle, and scan every label after it is applied: a two per cent misprint rate on 18,000 locations is 360 places where stock will be put away correctly and never found.

Distribution center startup checklists should require a 100 per cent scan audit of applied location labels against the WMS location master before Gate 3, because a 2 per cent label error rate on 18,000 locations leaves 360 slots where putaway confirms but picking cannot find stock.

Interface testing follows the same principle of proving it here. Receipt confirmations, ship confirmations, inventory adjustments and order downloads must run between this site's WMS instance and the ERP with real item masters and real carriers. Our ERP and WMS integration test script lists the cases; for a startup, add a radio-frequency coverage survey of every aisle end and mezzanine, and a print test of every label format on every printer.

Receiving the opening stock and proving it with a count

The opening inventory is the first real test of receiving. Bring it in on advance ship notices from the sending sites, count it completely, and let no customer order release against a location that has not been counted.

Schedule seed stock from Day minus 21, in loads small enough for the first wave to receive at a learning pace. Each inbound load should arrive with an advance ship notice built from the sending site's pick confirmations, so the receiving team can scan against an expected quantity. Where the sending site sits in another Indian state and the new site has its own GSTIN, the movement is a transfer between distinct registrations and needs the same tax documents as any other inter-state supply.

1. Day minus 21, 07:00: Load ST-0041 arrives with ASN 778201 for 26 pallets; the receiving team finds two pallets labelled with a SKU that is not in the new site's item master, because the item download excluded a product family.
2. Day minus 21, 09:30: A supervisor receives the two pallets to a dummy SKU to keep the dock clear; the WMS transaction is a manual receipt with no ASN line reference.
3. Day minus 7, 15:00: The opening count shows 26 pallets on hand but the dummy SKU has no orderable stock, so 1,120 units of a promoted item are invisible to order allocation.
4. Day 0, 06:00: Orders for the item backorder; customer service escalates at 10:15 and the stock is relabelled by hand at 13:40, after the carrier cut-off.
5. Controlled state: Receipts without a matching ASN line are blocked, unknown SKUs go to a held quarantine location, and the item master download is reconciled against the sending site's active SKU list at Gate 3.

Ramp curve from first order to full design volume

Step volume up in planned increments and move to the next step only when the site meets its exit tests at the current one. A curve of 25, 50, 75 and 100 per cent over eight weeks is a reasonable default for a conventional pallet and case operation.

The exit tests should be few and measurable: location-level inventory accuracy, on-time shipment against carrier cut-off, the end-of-shift backlog, and safety incidents. If a step misses its test, hold the volume for another week instead of adding people, because new labour added to a site that is still learning usually lowers productivity before it raises output.

Ramp curves for a new distribution center startup should step volume through 25, 50, 75 and 100 per cent in two-week blocks, advancing only after five consecutive days at 99.5 per cent location accuracy; in the illustrative US case the eight-week penalty is 3,246 extra picking hours, or $77,912.

The figures are illustrative and cover only the picking function, but the shape is general: half the ramp penalty falls in the first four weeks. Spending on a stronger launch team, more mock days and earlier operator evaluations attacks exactly those weeks, which is why those items tend to repay their cost even on a modest site.

Gate sign-offs and where planning software helps the launch team

Each gate needs a person who can say no, and that person should not be the one who did the work. Software helps forecast, schedule and flag; the release decisions stay with named people against fixed criteria.

Go or no-go checklist for the final ten days before launch

Hold a formal go or no-go review at Day minus 10 and again at Day minus 2. Every line must pass or carry a written workaround with an owner; a blank is a no.

This list is for a conventional distribution center serving stores, wholesale or e-commerce from pallet, case and each storage. It is a different exercise from choosing software for a small urban site; our micro-fulfillment center software buyer guide deals with that purchase decision, while this page covers the physical and organisational launch of a building.

If the launch needs WMS configuration, integration testing or ramp dashboards built for this site, describe the scope and dates in our startup support request. The wider set of warehouse and transport guides is in the logistics and supply chain collection.