Why Coupang Rocket Growth SKUs Stay Unavailable

A delivery scan at a Coupang fulfillment center confirms physical arrival, not sellable inventory. Your SKU remains out of stock until Coupang completes inbound processing and reconciliation, accepts the units as sellable, and posts that quantity as available. Pending, mismatched, or exception units cannot support the customer-facing Rocket promise.

The four Rocket Growth stages from dispatch to sale

Think of a Rocket Growth inbound as a chain of handoffs, not a single event called received. For practical planning, keep these four stages separate:

1. Dispatched or in transit. The shipment has left the origin and is moving through the carrier network. It may be counted in a transport plan, but it is not inventory that Coupang can allocate to a customer order.
2. Delivered to the fulfillment center. The carrier records arrival or handover at the Coupang fulfillment center. This confirms that the shipment reached the destination, but it does not by itself confirm that Coupang has finished opening, checking, and recording the inbound.
3. Received and reconciled. Coupang processes the inbound and compares what was expected with what was presented. Product identifiers, unit quantities, carton quantities, preparation, and product status can all matter during this handoff. Units may be accepted, remain pending, or be assigned to an exception rather than becoming sellable immediately.
4. Available for sale. The accepted sellable quantity is posted as available inventory. This is the state that can be allocated to an order and relied on when making a customer-facing Rocket delivery promise.

Delivery does not mean that every unit is available. A partially reconciled shipment may contain some available units while others remain pending or in exception. Forecast only the available portion.

Your account may not display these ideas with exactly the same four labels in every screen. A carrier event, a Seller Center inbound record, and an inventory field answer different questions. If one dashboard combines them, do not fill the gap by assumption. Check the inbound detail and the available quantity separately.

For the technical side, use Coupang's official Open API developer documentation as a primary source for the fields and behaviors exposed to your account. For physical preparation and receiving requirements, use the current instructions in Coupang's seller and fulfillment workflow; those instructions take priority over a generic warehouse checklist.

A carrier proof of delivery is therefore useful evidence, but it is not the final inventory signal. When the listing is still unavailable after delivery, the next question is not whether the parcel arrived. It is whether the inbound has been reconciled into sellable units.

Why a delivered inbound can still show zero available

The gap between delivery and availability is usually a receiving, data, preparation, or product-status issue rather than a simple freight issue. A shipment can be physically inside the fulfillment center and still lack an accepted quantity that Coupang can allocate.

• Receiving is still pending. The fulfillment center has custody of the shipment, but the inbound has not completed its receiving and reconciliation step. Until that process records sellable units, the customer-facing listing can remain unavailable.

• Expected and actual quantities do not match. The inbound instruction may specify one quantity while the physical shipment contains another. Unit counts, carton counts, or the product identifier attached to the shipment can create a discrepancy. The correct response is to reconcile the difference, not to treat the dispatched quantity as the received quantity.

• Units or cartons fail an applicable preparation or condition check. Coupang's receiving workflow can require preparation that makes the unit identifiable, intact, and retail-ready. A unit that does not meet the applicable instruction may be held as an exception even though the carton reached the correct building. Requirements vary by product and workflow, so use the current Coupang instructions rather than assuming that ordinary outbound packing is sufficient.

• The product or item has a catalog or eligibility exception. Physical arrival cannot correct an item that is not correctly set up, approved, or eligible for the relevant Rocket Growth workflow. A listing, variation, identifier, or product status problem can therefore keep inventory from becoming orderable after delivery.

• The shipment is only partially reconciled. Received, sellable, pending, and exception quantities can diverge. Some units may be accepted while others remain unresolved. Reading only the total shipment quantity hides the exact problem that is keeping the SKU below the level you expect.

A useful way to read the platform state is to pair each observation with the next operational question:

Do not collapse a lower available quantity into a carrier-loss conclusion too early. First separate the physical handoff from the platform reconciliation, then compare the records at SKU level. That approach tells you whether the next action is a receiving follow-up, a quantity correction, a preparation fix, or a product-status review.

For identifier problems, Why Coupang Rocket Growth Requires a Barcode on Every SKU explains why a unit-level barcode check matters before inbound. If the issue involves the receiving desk's label or certification review, Coupang Inbound Verification: Label & Cert Review is the more relevant diagnostic path.

The key discipline is to ask what happened to each expected unit. The shipment can be delivered while the answer for some units is still pending.

The inbound checklist: prevent holds and forecast correctly

The brand's responsibility does not end when the carrier accepts the cartons. The practical control is a two-part checklist: verify the inbound before dispatch, then reconcile the platform state after the carrier marks delivery.

Before the shipment leaves origin

• Verify the product setup. Confirm that the exact item, variation, product identifier, and listing are set up for the intended Rocket Growth workflow before shipping units. A product that is not correctly approved or eligible cannot become orderable simply because it arrived at the fulfillment center.

• Match the expected inbound record to the physical shipment. Record the SKU or approved product identifier, expected unit quantity, carton quantity, shipment reference, and destination. The packing list and the inbound instruction should describe the same shipment. Keep the record at SKU level so one correct line does not hide a different line's shortage or mismatch.

• Prepare units and cartons according to the current instructions. Apply the applicable unit and carton preparation, identification, and condition requirements. Units should arrive in a retail-ready state, with the required identifiers attached and readable where the workflow requires them. Do not substitute a general warehouse standard for the current Coupang instruction.

• Keep evidence that can resolve a variance. Retain the shipment reference, carrier tracking and proof of delivery, packing list, expected counts, and any available record of how the units and cartons were prepared. These records turn a vague statement that stock is missing into a specific comparison between expected, delivered, received, available, and exception quantities.

After the carrier marks the shipment delivered

1. Check Coupang's inbound and availability records. Do not close the inbound in your planning sheet when the carrier status changes to delivered. Open the platform-side record and capture the current receipt, available, pending, and exception information exposed to you.

2. Reconcile each quantity separately. At minimum, keep these fields distinct:

   Field	The question it answers
   Expected quantity	What did the inbound instruction say should arrive?
   Delivered quantity	What did the carrier record at the fulfillment center?
   Received or reconciled quantity	What did Coupang record during inbound processing?
   Available or sellable quantity	What can be allocated to customer orders now?
   Pending or exception quantity	What still needs processing, explanation, or correction?

3. Investigate the variance by SKU. If the available quantity does not match the expected quantity, compare the physical records and identifiers before making a replenishment decision. Ask which units are unresolved and why. A single shipment-level total is not enough when one product or variation is affected differently from another.

4. Keep unresolved stock outside the sellable forecast. Inventory that is in transit, awaiting receipt, or held as an exception may eventually become available, but it cannot support today's customer order. Include it in an inbound view if useful; do not include it in the quantity used to assess listing availability or the Rocket promise.

5. Replenish before available stock reaches zero. The trigger should be projected available-to-sell exhaustion, not dispatch and not delivery. Your planning window needs to account for transport plus the time required for Coupang to receive and reconcile the inbound. Rocket Growth Inbound Minimums and Real Lead Times is useful when sequencing those upstream steps.

A simple internal inventory view can therefore contain five separate columns: expected, delivered, received or reconciled, available, and pending or exception. That structure makes the handoff visible. It also prevents the common mistake of telling a sales or marketing team that replenishment has arrived when the only confirmed fact is that a carrier reached the dock.

Once units are accepted into available inventory, Coupang manages the fulfillment-center work of storage, picking, packing, and delivery. The brand still needs to maintain accurate product and quantity records, monitor availability, follow up on exceptions, and replenish before the sellable balance is exhausted. The operational boundary is clear: Coupang handles fulfillment after acceptance; the brand must not mistake arrival for acceptance.

If a system or integration encourages manual stock edits, remember that an edit does not establish that pending units were physically received and accepted. Why You Can't Push Stock Counts to Coupang Rocket Growth covers why the platform-side stock state must be tied to physical inbound rather than treated as a number that can simply be pushed into place.

Common questions about Coupang Rocket Growth stock

Does proof of delivery mean Coupang has received my inventory?

It means the carrier recorded delivery to the fulfillment center. It does not necessarily mean that Coupang has completed inbound receipt and reconciliation or posted units as available. Check the platform-side inbound and availability records.

Can a delivered shipment be partially sellable?

Yes. The accepted available quantity can differ from the total shipped or delivered quantity while other units remain pending or in exception. Forecast and promise only the available portion.

What should I do if Coupang received fewer units than I shipped?

Compare the expected, delivered, received or reconciled, available, and exception quantities at SKU level. Use the packing list, identifiers, and carrier evidence to document the variance, then follow up through the applicable Coupang inbound workflow rather than assuming the cause before reconciliation is complete.

Can I manually set the Rocket Growth stock count while receipt is pending?

No—not for unreceived or unresolved units. A catalog or inventory edit cannot establish that Coupang physically accepted those units as sellable; resolve the inbound state first.

When should a launch or replenishment be treated as ready?

When the relevant quantity appears as available for sale, not when the shipment is dispatched or marked delivered. Plan the replenishment trigger around projected available stock and include both transport and receipt-processing time in the planning window.

What happens after the units become available?

Coupang manages storage, picking, packing, and delivery through Rocket Growth. The brand remains responsible for monitoring sellable stock, reconciling exceptions, and sending correctly prepared replenishment before available inventory reaches zero.