A seller with a healthy 2-year-old account encountered a critical workflow blocker: the ‘Pack Individual Units’ button (Step 1b) in the FBA shipment creation process is greyed out, preventing progress to shipment packing. The issue persists across multiple browsers, incognito mode, and mobile access—ruling out standard browser/cache problems. The seller’s account health is clean, SKUs are valid, and warehouse capacity is only at 20%, so typical account or inventory restrictions don’t appear to apply.
What’s Happening
- Symptom: The grey button appears in the “Ready to Ship” section; clicking does nothing
- Variables tested: Multiple SKUs selected, different browsers (3+), incognito/private mode, mobile web access, cache/cookie cleared
- Account status: No holds, no restrictions, no known SKU issues
- Capacity: Only 20% of warehouse limit in use
Likely Causes & Next Steps
- Hidden account flags: Contact Seller Support directly—sometimes temporary holds or compliance reviews block shipment functions without displaying obvious warnings
- SKU-level blocks: Request a Seller Support review of each SKU in the shipment; even “clean” SKUs can have hidden flags
- Regional/marketplace quirks: If this is UK-specific (as the title suggests), check if there are pending compliance documents or region-specific shipment requirements
- AWS/API layer issue: Rare, but a backend service outage can grey out buttons; Seller Support can confirm
How Squatio Helps
When troubleshooting shipment workflow issues, having clarity on your SKU health and listing status across ASIN records can help you identify whether a specific product is the culprit before contacting support. Squatio Decode (ASIN lookup, listing visibility & Sentiment IQ review analysis) lets you quickly pull full listing visibility, suppression status, and review sentiment for each SKU in the blocked shipment—helping you spot any hidden compliance or visibility issues that might be causing the workflow gate to lock.
Have you encountered workflow blockers in your FBA shipment creation process? What triggered the issue, and did Seller Support identify a root cause?
Source: Reddit