Guide · Wayfair CastleGate
CastleGate is not one warehouse, it is Wayfair's distribution network, and InfiPlex can sync it two different ways. Pooled sync collapses every CastleGate location into a single InfiPlex warehouse record, which is simple but throws away the one piece of information that actually helps you win orders: which specific CastleGate facility holds the stock. 1:1 sync keeps every CastleGate warehouse as its own location in InfiPlex, and that distinction is what lets a marketplace like Amazon promise faster delivery on inventory it knows is positioned close to the buyer, which means more orders, not just cleaner data.
Two ways to sync
CastleGate is Wayfair's own fulfillment network: multiple distribution centers positioned around the country, holding inventory forward so Wayfair can ship it fast. When InfiPlex connects to a CastleGate account, there are two fundamentally different ways to represent that network internally. Pooled sync (labeled Selected Warehouse in the connection settings) collapses every CastleGate DC into a single InfiPlex warehouse; whatever quantity CastleGate reports across all of its locations combined shows up as one number against one warehouse record. 1:1 sync (Specified Warehouses) keeps each CastleGate warehouse ID as its own distinct InfiPlex warehouse, with its own tracked quantity, updated separately.
InfiPlex's own connection settings flag the pooled option as not recommended, for exactly the reason this page covers: pooling throws away information that a well-connected multichannel operation can actually use to win more orders.
Why 1:1 matters
When CastleGate inventory is pooled into one warehouse, every marketplace you sell on sees a single quantity with no location attached to it. When it is synced 1:1, each CastleGate warehouse is a real, named location in your OMS, with its own quantity, the same as any other warehouse or 3PL you run. That distinction matters because modern marketplaces increasingly let sellers report inventory by location rather than as one blended total, specifically so the marketplace can promise faster delivery on inventory it knows sits close to a given buyer.
Amazon's version of this is Supply Sources: a seller with 1:1 CastleGate warehouses can map each one to its own Amazon Supply Source, so Amazon's delivery-date logic sees CastleGate inventory the same way it would see any other regional fulfillment location, not as one undifferentiated pool. Faster promised delivery on a listing translates directly into more orders on that listing, which is the actual business case for 1:1 sync, not just tidier inventory records. The same logic applies on any other marketplace that supports multi-location inventory, not only Amazon; wherever that feature exists, pooled CastleGate data cannot feed it and 1:1 data can.
The Amazon multi-location inventory setup guide covers the Amazon side of this in detail.
Mechanics
| Setting | What it controls |
|---|---|
| How to Sync Inventory: Specified Warehouses | Each CastleGate warehouse ID (for example, a facility labeled wayfair1) is tracked as its own InfiPlex warehouse, with its own quantity per SKU |
| Fulfillment Inventory per warehouse | InfiPlex holds a distinct quantity for every SKU at every CastleGate warehouse ID, not one combined figure |
| Hours Between Inventory Pulls | Controls how often the full CastleGate catalog is re-pulled; since the entire product list pulls every cycle, sellers with large catalogs should widen this interval rather than pull continuously |
| SKU mapping direction | Order pushes use InfiPlex SKU to CastleGate SKU; inventory pulls use the reverse, CastleGate SKU to InfiPlex SKU |
Once 1:1 sync is running, every CastleGate warehouse behaves like any other location in your operation: it has its own address in your OMS, its own inventory ledger per SKU, and it becomes eligible to receive routed orders, or to feed a marketplace's own per-location inventory feature, exactly like a warehouse you operate yourself.
At the order level
1:1 sync is also what makes intelligent order routing across CastleGate possible in the first place: with each warehouse tracked separately, InfiPlex's routing rules can decide which specific CastleGate facility should fulfill a given order, and a single order can even split across more than one CastleGate warehouse when that is the correct fulfillment path. That mechanic, and the alternative of simply handing an order to CastleGate and letting Wayfair pick the warehouse, is covered in full in the order routing and split shipments guide.
Automation
InfiPlex configures CastleGate as 1:1 by default when the goal is marketplace multi-location inventory or warehouse-aware order routing, mapping each CastleGate warehouse ID to its own InfiPlex location and, where applicable, to its own Amazon Supply Source or equivalent on other marketplaces. Program page: Wayfair CastleGate integration.
Frequently asked
The questions sellers ask when deciding how to sync CastleGate inventory.
Pooled sync (Selected Warehouse) reports all CastleGate inventory under one InfiPlex warehouse. 1:1 sync (Specified Warehouses) tracks each CastleGate distribution center as its own InfiPlex warehouse with its own quantity per SKU.
1:1 (Specified Warehouses). The pooled option is explicitly flagged as not recommended in the connection settings.
Because it gives marketplaces location-level inventory data instead of one blended number. Amazon, for example, can map each 1:1 CastleGate warehouse to its own Supply Source and promise faster delivery on inventory it knows is positioned close to the buyer, and faster promised delivery increases orders on that listing.
No. Any marketplace with a multi-location inventory feature can only take advantage of it if the underlying CastleGate data is tracked per warehouse. Pooled data cannot feed that kind of feature on any marketplace; 1:1 data can, on whichever marketplaces support it.
On a configurable interval; the full product catalog pulls every cycle rather than only changes, so sellers with large catalogs typically widen the interval rather than pulling continuously.
The SKU mapping mechanism is the same either way: InfiPlex SKU to CastleGate SKU for order pushes, and the reverse for inventory pulls. What changes with 1:1 is that inventory quantities are tracked per CastleGate warehouse rather than combined.
Yes, though it is a configuration change in the CastleGate connection settings, mapping each CastleGate warehouse ID to its own InfiPlex warehouse rather than one shared record.
Yes. With each warehouse tracked separately, InfiPlex's routing rules can direct orders, or parts of an order, to the specific CastleGate warehouse best positioned to fulfill them, rather than only being able to hand the whole order to CastleGate as one block.
Resources
1:1 inventory sync feeding Amazon Supply Sources and every other marketplace's multi-location inventory. Live in 1–3 business days.
We set up 1:1 CastleGate sync every week, mapped to Amazon Supply Sources and equivalent features elsewhere. Tell us your current setup and we will map the switch. Contact us, email info@infiplex.com, or call 888‑770‑0857.
InfiPlex™ is a trademark of InfiPlex. Wayfair, Wayfair CastleGate, and Wayfair Professional are trademarks of Wayfair LLC or its affiliates. Amazon and other names are trademarks of their respective owners. InfiPlex is an independent integration provider and is not endorsed by or affiliated with Wayfair or Amazon. Program rules, warehouse networks, and settings referenced here are set by Wayfair and Amazon respectively and change; verify current terms in your Wayfair Vendor and Amazon Seller Central accounts before relying on them. ©2026 InfiPlex. All rights reserved.
InfiPlex provides eCommerce companies, warehouses, and 3PLs with a robust platform to manage their sales channels.
©2026. All Rights Reserved. Privacy Policy | Terms & License