Our Journey Of Integrating Amazon with ERPNext in 9 Months
summary
Started as a 30-day sprint and stretched to a 9-month rewrite, building the open-source Amazon e-Seller App on ERPNext/Frappe that syncs orders, payments and inventory; teams re-architect multiple times, implement order-to-invoice logic, and add a custom payments reconciler to handle dozens of payout cases. Key failures and fixes: a time-zone bug (UTC vs IST) that dropped orders, ghost orders from years prior, server outages, Amazon SP API access restrictions and FBA stock-transfer quirks — final app works with workarounds but some ledger-edge cases remain unresolved.
AI-written summary · about
chapters (11)
- 0:00Introduction and team
- 3:37Project requirements and challenges
- 4:44Order handling issues
- 6:52Time zone and data sync problems
- 7:55Invoice and ledger integration
- 8:15Payment data integration hurdles
- 9:21Missing ledger entries mystery
- 10:43Server failures and stock handling
- 11:45Ghost orders and compliance
- 12:49Lessons learned and future plans
- 15:01Q&A session
related talks
15mHeadless E-commerce using ERPNext and JAMStack
20mAPIfying an ERP
27mApidays Virtual Helsinki - Andrew McCauley, Shopify
29mBuild full-stack web and mobile apps with AWS Amplify and AWS AppSync
20mThe story of Fyndiq's API
26mMastering API Platforms for Enhanced Payment Integration
26mDelivering connected digital experiences with APIs
15mThe E-Mall pt.3