• Home
  • 3PL WMS Requirements Checklist: Document Each Client’s Rules

3PL WMS Requirements Checklist: Document Each Client’s Rules

Warehouse Management Systems
Warehouse manager choosing the right 3PL software for fulfillment operations

A warehouse manager may say, “We need separate inventory for every client.” That sounds straightforward until two clients use the same SKU code, one requires lot tracking, and another needs returned products held until someone approves them for resale.

These details belong in your 3PL WMS requirements checklist before you contact software providers. Otherwise, important rules tend to surface during configuration, when changing the scope can delay the project or create additional work.

The checklist should describe what each client needs, which rules apply across the warehouse, and what must happen when a normal process cannot continue. A feature name alone rarely captures enough detail.

Start With the Client Agreements and Daily Work

Bring together the people who receive stock, supervise fulfillment, manage client accounts, prepare invoices, and maintain integrations. Each team sees requirements that may be missing from the others’ records.

Account managers may know that a client expects a daily inventory report. Warehouse staff may know that the same client sends cartons without consistent labels. Finance may know that repacking is chargeable but rarely appears on the activity report.

Review client agreements alongside the work actually being performed. Where they differ, resolve the requirement rather than building the current workaround into the new system.

For each client, record:

  • Products, identifiers, storage conditions, and traceability needs.
  • Order sources, fulfillment instructions, and dispatch commitments.
  • Return inspection and disposition rules.
  • Agreed service charges and billing periods.
  • User access, reporting needs, and approval responsibilities.

Include a demanding account as well as a straightforward one. Requirements based only on your easiest client can leave significant gaps.

Define Inventory Ownership Beyond the SKU

A shared warehouse must distinguish between the product and the client that owns it.

Suppose two clients both use the code CASE-BLACK. Your requirement should explain how receiving staff identify the owner, how stock remains associated with that account, and which inventory can be allocated when an order arrives.

Also document the inventory details each account needs. One client may require lot numbers and expiration dates. Another may need serial numbers, pallet references, or carton-level records.

Stock status matters just as much as quantity. Define when goods become available for allocation and which conditions keep them unavailable. Damaged receipts, unresolved discrepancies, inspection holds, and returned goods should have agreed handling rules.

For a broader explanation of the capabilities involved, see our 3PL WMS features guide.

Describe the Rules That Change by Client

“Supports picking and packing” does not explain whether the system can handle different client instructions within the same operation.

Document the differences that staff currently remember, print separately, or receive through messages. These might include a required insert, a specific carton, a lot-selection rule, a wholesale packing document, or approval before a partial shipment.

Use a working requirements table rather than a long list of feature names:

AreaClient-specific requirementException to document
ReceivingClient A requires a lot number for every receiptRequired lot information is missing
InventoryIdentical SKU codes can exist under different clientsAn order cannot be matched to its owner
PackingClient B requires an insert for selected ordersThe required insert is unavailable
ReturnsClient C approves returned stock before resaleInspection is complete but approval is pending
BillingRepacking is charged under the agreed rate cardWork is recorded without a valid rate

The exception column is useful because it identifies where staff need a clear decision. Record whether work should stop, continue with a warning, or move to an approval queue, and identify who owns that decision.

Turn Billing Agreements Into Specific Requirements

Do not stop at “automated billing required.” Write down what creates a charge and how the amount should be calculated.

For storage, specify the agreed measurement and timing. A client might pay by pallet position, bin, unit, or another defined basis. The agreement should explain which inventory is included and how changes during the billing period affect the calculation.

For handling services, distinguish receiving, order processing, additional picks, packaging, labeling, kitting, returns, and other agreed activities.

An inventory movement does not automatically create a billable charge. Charging depends on the client agreement, recorded activity, and applicable pricing rule.

Document who can change rates, review calculated charges, approve adjustments, and prepare information for finance. Keep the original activity traceable when a charge is corrected.

Our 3PL billing software page explains how warehouse activity and client rates can connect within the billing process.

Map Each Client’s Connected Systems

A platform name is only the beginning of an integration requirement.

For each client connection, record which system supplies product information, which orders should enter fulfillment, how inventory availability is calculated, and which shipment updates must return to the channel.

Include changes that happen after the original order arrives. Cancellations, address changes, partial shipments, and duplicate messages can affect warehouse work differently depending on the order’s current stage.

Assign responsibility for failed updates. If an order does not import, someone needs to know where the error appears, who investigates it, and how it can be retried without creating a duplicate.

Record any manual file exchanges too. A spreadsheet upload used once a week can still be a critical client requirement.

Specify Client Access and Reporting

“Client portal required” leaves several questions unanswered.

Define what each client user can view and do. One account may only need inventory and shipment visibility. Another may need to submit inbound shipment details, download reports, or request changes.

Separate client permissions from warehouse staff permissions. Document access by account, warehouse, role, and action where those restrictions are needed.

Reporting requirements should name the question being answered. “Show unshipped orders approaching today’s cutoff” is clearer than “operational dashboard required.”

For each important report, identify its audience, required fields, reporting period, and delivery method. Confirm whether the client needs current information, a scheduled summary, or an export for another system.

Separate Launch Requirements From Future Needs

A useful checklist makes priorities visible.

Mark each requirement as essential for launch, desirable, or planned for a later phase. Add the responsible person and identify any unresolved client decision.

Do not classify an existing contractual obligation as optional simply because it is difficult to configure. Equally, avoid making a possible future service a launch dependency without a clear business reason.

Before sharing the checklist, have operations, client services, finance, and the integration owner review their sections. Resolve contradictory instructions and make assumptions explicit.

You should finish with a document that explains the work, account-specific differences, exceptions, owners, and launch priorities. That gives vendors something concrete to respond to.

Once those requirements are agreed, use our guide on how to choose a 3PL WMS to plan demonstrations and compare shortlisted providers.

Discuss Your Requirements With Fulfillor

If you are evaluating Fulfillor, bring examples of your client workflows, billing agreements, integration needs, and recurring exceptions.

Schedule a walkthrough to discuss those requirements and identify what needs configuration, further review, or additional development.