Краткий ответ: A tender for a fulfillment warehouse must describe the range of products, the order profile, the receiving process, storage requirements, pick/pack rules, stock control, returns, integrations and reporting. The buyer should ask each provider to state what is included, which assumptions affect fees or service levels, and how exceptions are handled. A comparable scope enables the merchant to evaluate operations before inventory is transferred.
Describe the product and order profile
Indicate the number of SKUs, dimensions, weight, variants, kits, fragile or special-handling items, and expected order lines. Provide normal and peak volumes with the time period and source of each estimate. Distinguish forecasts from observed history. A warehouse proposal based on a daily total of orders can hide differences in pick complexity or SKU density. This profile helps the provider explain the storage, labor and process assumptions behind the proposal, and allows the merchant to compare offers against the same operating picture.
Define receiving and onboarding of inventory
Explain how incoming shipments are declared, labeled, counted and reconciled with the purchase order or packing list. State what evidence is required for shortages, damage or unknown SKUs. Include how barcodes, variants and unit-of-measure records are validated before stock is made available. Ask the provider to identify what the merchant must provide before an arrival. A clear receiving scope prevents the warehouse from guessing product identity and gives both teams a common rule for resolving discrepancies.
Specify storage and stock control
Describe which products require bins, shelving, pallet locations, lot information, expiry handling or another agreed control. Ask the provider how locations and stock status are displayed in the system, and how available inventory differs from held or damaged units. State storage limitations and the records required to release a hold. Do not assume that all SKUs use the same location or counting method. A written stock policy makes it easier to understand how inventory is protected and how adjustments reach the merchant’s sales channel.
Map order release, picking and packing
Document how orders are sent, which events make them eligible for picking, and how variants, bundles, inserts and gift messages are processed. Define the pick-verification step and the packaging materials expected for each item group. If orders can be split across parcels, state how tracking and item contents are reported. Ask the provider to list exclusions, such as special packaging or manual review. These details allow merchants to compare actual workflows, not generic promises to pick and pack orders.
Set rules for changes, holds and exceptions
Enumerate what occurs when an order contains invalid data, missing inventory, a damaged item, an unknown barcode, or a duplicate request. Specify who approves substitutions, order edits, inventory adjustments, and urgent holds. Define how the warehouse communicates with the merchant and what information a case includes. A provider should explain which exceptions halt processing and which can follow an approved path. This enables customer service to provide accurate updates without requiring warehouse staff to improvise.
Compare integrations and reporting
Identify the commerce, order, inventory, and carrier systems that need to be connected. Inquire which data fields synchronize, how often updates occur, and where errors are reported. Request sample reports for orders, inventory, receiving, returns, and exceptions. Agree on definitions for metrics such as processing time and inventory accuracy before comparing providers. A dashboard metric is not useful if one warehouse counts the event differently from another. The RFP should clarify data ownership and support contacts.
Review fees, capacity, and service assumptions
Ask each provider to itemize the fee basis for receiving, storage, pick lines, packaging, returns, projects, and other requested work. State which assumptions can change the estimate, including SKU count, storage cube, order profile, labor peaks, and special handling. Request a capacity plan for the forecasted peak and the supporting evidence. Do not compare a base rate with an all-in estimate without adjusting for scope. A consistent cost model supports a practical discussion of service and operational trade-offs.
Plan the transition and first-month review
Agree on data files, stock transfer, SKU tests, order validation, cutover owner, and fallback plan. Define a small launch cohort and what the warehouse reports daily during transition. Record open configuration issues before switching to full volume. After launch, compare actual receiving, inventory, order, and exception results with RFP assumptions. A scheduled review allows both teams to adjust the process while the first shipment history is still easy to investigate.
Для покупателей, сравнивающих доступные варианты товаров и поставщиков, смотрите Услуги по выполнению заказов со склада Dropioneer.
Вопросы, которые часто задают покупатели
Что должен включить торговец в запрос предложений (RFP) для склада по выполнению заказов?
Include SKU and order profiles, receiving, storage, pick and pack rules, returns, integrations, reports, fees, and exception ownership.
Как можно объективно сравнить предложения со складов?
Give each provider the same product, volume, scope, and service assumptions, then compare exclusions and fee definitions.
Какие метрики следует определить до подписания?
Agree on event definitions, population, time window, and data source for processing time, accuracy, and exception measures.
Что должно произойти до полного перехода (cutover)?
Validate SKU data, inbound inventory, order flow, pack rules, reporting, and a named fallback process with a controlled launch cohort.
