Inventory Aggregation Rules

Overview

Inventory Aggregation Rules let you combine inventory quantities from multiple Amazon SKUs into a single target SKU during inventory sync. This is useful when you sell a product under one SKU in your system but track it across multiple Amazon SKUs — for example, when the same product is listed under different FNSKUs, bundle variations, or regional listings.

When a rule is active, the source SKUs are automatically suppressed from the inventory sync output and replaced by a single computed target SKU with aggregated quantities.

When to Use This

Common scenarios where aggregation rules are helpful:

• Multi-pack or bundle consolidation — You sell a product as a single unit, but Amazon tracks inventory across a single-pack SKU and a multi-pack SKU. You want your system to see one combined inventory number.
• Regional or marketplace variants — The same physical product is listed under different Amazon SKUs across marketplaces, but you manage a single inventory count internally.
• SKU migration — You're transitioning from old SKUs to new ones and want inventory from both to feed into one target during the cutover period.

How It Works

Each aggregation rule has three components:

Available Operations

SUM is the default and most commonly used operation.

What Gets Aggregated

The aggregation applies across all inventory quantity fields reported by Amazon, including:

• Total quantity
• Fulfillable quantity
• Inbound quantities (working, shipped, receiving)
• Reserved quantities (pending orders, transshipment, FC processing)
• Unfulfillable quantities (damaged, defective, expired)
• Researching quantity
• Future supply quantity

Each of these fields is independently aggregated using your selected operation.

Configuration

1. In the Amazon MCF connector settings, find the Inventory Aggregation Rules section
2. Click to add a new rule
3. Fill in the fields:
   • Operation — Select how quantities should be combined (default: SUM)
   • Source SKUs — Enter the Amazon SKUs to aggregate from (add one per line)
   • Target SKU — Enter the SKU that should appear in your inventory sync
4. Save the connector settings

You can define multiple rules. Each rule operates independently.

Example Configuration

Scenario: You have a product sold individually (WIDGET-1PK) and as a 3-pack (WIDGET-3PK). You want your system to see total available inventory under WIDGET-COMBINED.

If Amazon reports:

• WIDGET-1PK: 50 units fulfillable
• WIDGET-3PK: 25 units fulfillable

Your inventory sync will show:

• WIDGET-COMBINED: 75 units fulfillable

Neither WIDGET-1PK nor WIDGET-3PK will appear in the sync output — they are replaced by the aggregated target.

Behavior Details

Source SKU Suppression

When a source SKU appears in the inventory feed from Amazon, it is not passed through to Pipe17. Only the computed target SKU is emitted. This prevents double-counting.

Real-Time Events

Aggregation rules also apply to real-time inventory event notifications. When Amazon sends an inventory update for a source SKU, the connector automatically fetches the latest quantities for all other source SKUs in the same rule, recomputes the aggregate, and emits the updated target SKU.

Blank Box Inventory

If your connector uses blank box (multi-channel fulfillment) inventory tracking, aggregation rules apply there as well. The connector fetches blank box quantities for each source SKU and aggregates them under the target SKU using the same operation.

Missing Source SKUs

If a source SKU has no inventory data in Amazon (e.g., new listing not yet received at FBA), it is treated as having zero quantity. The aggregation still proceeds with the available sources.

Multiple Marketplaces

Aggregation is applied per marketplace. If you sync inventory across multiple Amazon marketplaces, each marketplace's inventory is aggregated independently using the same rules.

Limitations

• A source SKU can only belong to one aggregation rule. If the same SKU appears in multiple rules, only the first matching rule applies.
• The target SKU does not need to exist as an actual Amazon listing — it can be a virtual SKU used only in your system.
• Changes to aggregation rules take effect on the next inventory sync cycle (typically within 5 minutes).
• Aggregation is applied after SKU filtering. If you have an inventory SKU filter configured, make sure source SKUs are not excluded by the filter.

Troubleshooting