Trace the service boundary
Follow inbound receiving, putaway, inventory storage, order release, picking, packing, and carrier handoff. Add returns and retail preparation where needed. Ask who owns each activity outside the standard flow.
Separate execution from ownership
Outsourcing warehouse execution does not remove the brand’s responsibility for product data, replenishment decisions, or customer promises. A useful service agreement makes those responsibilities explicit, including the information each team must supply.
Follow one unit through the operation
Start with an incoming product and trace receipt, stock availability, order allocation, picking, packing, dispatch, and a possible return. Name the system record and human owner at each handoff. List the decisions your brand retains, such as replenishment, customer promises, and product instructions. This exercise helps turn a broad fulfillment service description into a division of work both teams can discuss.
Review the operating tradeoff
Compare the effect on cost, inventory, and service scope together. Record the assumptions that would change the decision, not just the option that currently looks attractive. Ask for a baseline and one alternative so the consequences of the choice remain visible. A useful business case can be revisited when demand, product mix, or warehouse requirements change.
Use this question in your next meeting:
Which event changes the stock or order status, and who can resolve an exception?
Go deeper: One warehouse or two? Build the inventory case first. The companion article includes an editable worksheet and links to provider profiles.
Further reading
Shopify: inventory states. Reference for the distinction between available, committed, and other inventory states.