Skip to main content

‘SKU Adjustment’ Column in Planyard's Forecasting

Understanding the ‘SKU Adjustment’ Column in Planyard's Forecasting SideBar

A
Written by Abe Werzberger
Updated over 5 months ago


Why Is My FBA Stock Different From SKU Adjustments?

In Planyard, FBA Stock displays the total units available (or inbound) to Amazon for a product/SKU. SKU Adjustment shows how many of those units will offset your next purchase recommendation. Sometimes, SKU Adjustment is lower than your total FBA Stock, typically for two reasons:


1. SKU Demand is Lower Than Available FBA Stock

Example (Multiple SKUs)

  • SKU A

    • FBA Stock: 500 units

    • Demand: 2 units/day × 30 days = 60 total needed

  • SKU B

    • FBA Stock: 150 units

    • Demand: 10 units/day × 30 days = 300 total needed

Even though the total FBA Stock across these two SKUs is 650 (500 + 150) and the combined demand is 360 (60 + 300), SKU B doesn’t benefit from the surplus 440 units of SKU A’s stock. Each SKU’s FBA stock is SKU-specific, so SKU A’s overstock can’t offset SKU B’s understock.

  • SKU Adjustment for A: Up to 60 units (all it needs).

  • SKU Adjustment for B: Only up to its 150 available, falling short of the 300 it demands.


2. Lead Time Consumes Some of the FBA Stock

Example

  • Daily Sales: 10 units

  • Lead Time: 30 days

  • FBA Stock: 500 units

If Planyard projects you need at least 300 units to cover those 30 days (10 units/day × 30 days), it effectively “reserves” that portion. This leaves 200 to count toward reducing your next order.


Key Takeaway

  • FBA Stock = the total amount currently in or inbound to Amazon for that specific SKU.

  • SKU Adjustment = the portion of that stock Planyard uses to reduce new purchase orders, factoring in the SKU’s own demand and any lead times.

Because SKU A’s extra units can’t compensate for SKU B’s shortfall, you’ll see SKU Adjustment is calculated per SKU—leading to scenarios where surplus in one doesn’t offset another’s deficit.


If you still have questions, feel free to contact our Support Team. We’re here to help!

Did this answer your question?