I will build an amazon fba restock planner in google sheets with sp api
AI Automation and n8n Workflow Specialist
About this Gig
Still deciding what to reorder from a spreadsheet you update by hand? I build a Google Sheets restock planner that fills itself every morning.
Recent project, a real client: an apparel brand on Amazon FBA and regional marketplaces, about 300 SKUs, one main warehouse plus FBA.
- Every morning Make.com pulls warehouse stock and 30-day sales from the OMS, FBA stock from Amazon SP-API and open purchase orders from a Drive folder
- Each SKU gets an order quantity from sales speed, season, lead time, stock and MOQ
- Drop a PO into "Arrived" or a shipment file into "To FBA", and warehouse stock in the OMS updates. Each file is applied once and logged
- Every weekday a Sellerboard inventory export gets warehouse stock filled in, ready to upload
What you get:
- A Google Sheet you own, with open formulas and a guide for your team
- Make.com scenarios in your own account, with error emails
- SKU codes matched across your OMS, Amazon and supplier files
- A check on your real data before handover
Send me your sales channels, where your stock lives and how you reorder today. I will reply with a plan and a fixed price.
Programming language:
Python
Technology:
Excel
•
Google Sheets
Expertise:
Business Insights
My Portfolio
FAQ
Do I need a paid Make.com plan?
Yes. The scenarios run in your own Make.com account, so you own them. For about 300 SKUs the Core plan was enough: all three automations used about a third of its monthly credits.
Which inventory systems can you connect?
Any OMS or inventory tool with a REST API, plus CSV or Excel exports. Amazon FBA stock comes from Amazon SP-API through a read-only connection that you create in Make with my guide.
Is this AI forecasting?
No. It is a clear rule you can read in the sheet: sales speed, season, lead time, stock, open orders and MOQ. Your team can change every setting without me.
How do you get access without passwords?
You invite me to your Make team and create the Amazon and Google connections yourself. API keys go straight into Make, never into the chat.
What happens if something fails?
Make emails you and me. The sheet keeps the last good data, and a stock file with a bad row is rejected before anything is written.

