End-to-end FBA workflow automation.
StockFBA automates the end-to-end FBA workflow for Amazon sellers: sales forecasts, purchase orders, supplier check-in, FBA shipment creation, and per-SKU landed cost tracking. Built around the operational loop most FBA tools fragment into five different subscriptions.
Supplier check-in and warehouse receiving in one loop
True landed cost — fees, shipping, repack labor, all in
StockFBA integrates with Amazon's Selling Partner API to read seller-side catalog, inventory, order, and financial data. No buyer PII is ever requested or stored.
- Restock recommendations
- Demand forecasts (weighted MA)
- True per-SKU landed cost
- Slow-mover detection
- Inbound FBA shipment workflow
- No buyer PII, ever
The operational loop most tools fragment.
Most FBA tools stop at one step — forecasts in one app, purchase orders in another, supplier check-in on a spreadsheet, shipments in Seller Central. StockFBA connects the full loop from forecast through supplier delivery, warehouse receiving, FBA shipment creation, and landed-cost tracking so stock-on-hand and restock signals reflect what is actually in your building, not just what Amazon has received.
The other half of what makes StockFBA different is landed-cost transparency. Most tools stop at unit cost. We pull every Amazon fee — referral, FBA fulfillment, monthly storage, settlement adjustments — and compose them with your inbound shipping, repack materials, and repack labor to show the actual net profit per SKU. The number you'd see if you closed your books today.
How each SP-API role powers a StockFBA feature.
StockFBA requests seven non-restricted SP-API roles. Each one is tied to a specific feature sellers see in the application. We do not request the Restricted Data Permissions role because StockFBA does not need buyer PII to operate.
Catalog management
Reads SKU, ASIN, and FNSKU catalog data plus product attributes to map seller-side cost data — case-pack quantities, supplier SKUs, repack materials, prep labor — onto Amazon's catalog identifiers. Updates listing attributes when sellers edit them in StockFBA.
Margin analysis at current list price
Reads current listing prices to compute true landed-cost margin per SKU. v1 is read-only — no automated repricing — so pricing data is used strictly for profitability analysis and per-SKU economics screens.
Inbound FBA shipment workflow
Creates, updates, and queries inbound FBA shipments. Manages the multi-stage lifecycle from purchase order, through supplier delivery and warehouse receiving at the seller's facility, through tendering to Amazon, all the way to receipt at the fulfillment center.
Restock engine + sales velocity
Reads current FBA inventory levels (available, reserved, inbound, researching, unfulfillable) per SKU and per fulfillment center, plus historical order data, to compute sales velocity and demand forecasts. Drives the restock recommendation engine. Order data is aggregated to seller-side metrics — no buyer PII is retrieved.
True landed cost & per-SKU profit
Reads Amazon's fee statements and financial events — referral fees, FBA fulfillment fees, monthly storage fees, settlement summaries — and composes them with the seller's inbound shipping, repack materials, and prep-labor inputs to produce true per-unit landed cost and per-SKU net profit. Required for the landed-cost transparency feature.
Aggregate sales & inventory analytics
Reads aggregated sales and inventory data to inform demand-forecasting models and to identify slow-moving SKUs that need liquidation or markdown action ahead of Amazon's long-term storage fee cliff at day 181. See the dedicated Brand Analytics section below for a full description.
Account-health context
Reads seller account performance metrics to surface account-health context alongside inventory recommendations — so a restock decision can factor in whether the seller account is in good standing or has open issues that might delay receiving.
What we do with Brand Analytics data.
Brand Analytics is the most data-sensitive role StockFBA requests, so we describe its use explicitly. We use Brand Analytics aggregate sales and inventory data for two purposes, both internal to the authorized seller's StockFBA account:
- Demand forecasting. Aggregated historical sales drive the weighted-moving-average forecast that powers StockFBA's restock recommendation engine. The forecast is shown only to the seller whose data produced it; no cross-seller analytics are surfaced and no comparative benchmarks across sellers are computed.
- Slow-mover identification. Aggregate inventory and sell-through data is used to flag SKUs that are slowing (4-week velocity below 50% of 90-day baseline) or stuck (more than 180 days of cover, ahead of Amazon's long-term storage fee cliff). The seller sees a list of action candidates; no automated liquidation is performed.
Transparent tiers, no surprises.
Pricing is per-tenant per month. SKU-count tiers reflect StockFBA's compute footprint (forecasts, fee composition, snapshot retention) — they're a fair proxy for how much the app does for you, not a usage-meter gotcha.
- Restock recommendations
- Demand forecasts
- True landed cost per SKU
- Inbound FBA shipment workflow
- Supplier check-in & warehouse receiving
- Slow-mover detection
- Email + in-app alerts
- Everything in Starter
- Daily price + stock snapshots
- Brand Analytics features
- Account-health context
- Per-tenant webhook destination
- 14-day no-card trial
- Everything in Growth
- Multi-marketplace (UK / DE / etc.) when supported
- Custom SLA
- Volume discount
- Priority onboarding
No setup fees. No required add-ons. The published tier price is what you pay. Cancel any time; data exports available on request. Pricing reflects current StockFBA beta phase and may be revised at general availability with at least 30 days notice to active subscribers.
What we read, store, and protect.
StockFBA reads seller-side Amazon data only — catalog, inventory, orders aggregated to seller metrics, fees, listing prices, brand-analytics aggregates, account performance. We do not request the Restricted Data Permissions role; buyer names, addresses, phone numbers, and emails are never read or stored.
All Amazon data is encrypted at rest (AES-256 in production cloud storage; FileVault
disk encryption in development) and in transit (TLS). LWA refresh tokens are stored in
a managed secrets vault in production and a mode-0600 file in development; credentials
are never committed to source control or hard-coded into the application. We maintain
a written incident response plan with defined roles and 24-hour notification to
security@amazon.com for any incident involving Amazon data.
StockFBA is in private beta.
We're onboarding sellers carefully — currently US-marketplace private-label FBA in the $5K to $100K per month revenue range. If that fits, send a note and we'll talk about access timing.
Alex Medin DBA Alexsnet · 1441 Plunkett St, Hollywood, FL 33020 · United States