About the Client
The client is a growing e-commerce business that sells through Amazon’s marketplace and runs its operations on NetSuite ERP. As order volumes increased, keeping Amazon and NetSuite in step by hand was slowing the business down and putting customer experience at risk.
The Challenge
Amazon and NetSuite weren’t connected, so the team was bridging the gap manually. That created three problems.
Manual Data Entry
Every Amazon order was entered into NetSuite by hand, which caused delays and a high risk of errors.
Inventory Mismatch
Without real-time inventory updates, the business often oversold products or ran out of stock, which hurt customer satisfaction.
Disconnected Systems
Customer data lived separately in Amazon and NetSuite, creating inefficiencies and making a seamless customer experience difficult.
The Solution
LST Consultancy built an Amazon NetSuite integration using NetSuite Connector, Oracle’s connector for linking NetSuite to marketplaces, supported by custom middleware and scripts. It has four core components.
Amazon Marketplace
Orders, stock and sales
- Order 112-48212 items · PrimeNew
- Order 112-48221 item · StandardNew
- Order 112-48233 items · EURPaid
- Order 112-48241 item · PromoPaid
NetSuite Connector + middleware
- Queue
- Batch
- Mapping rules
- Retries
Oracle NetSuite
Single source of truth
- Sales ordersCreated automatically
- InventoryUpdated from every sale
- CustomersOne unified profile
- FinancialsSales data ready to reconcile
Order Sync
Amazon orders import into NetSuite automatically, complete with customer details, shipping information and payment status.
Inventory Management
NetSuite inventory levels update automatically based on Amazon sales, keeping stock figures accurate and reducing overselling and stockouts.
Customer Data Sync
Customer details from Amazon sync into NetSuite, creating a single, unified customer profile for better customer relationship management and more personalized marketing.
Financial Integration
Amazon sales data flows into NetSuite’s financial module, supporting accurate, timely financial reporting and faster reconciliation.
The integration was also designed to scale, so it can handle higher transaction volumes as the business grows.
How We Delivered It
We delivered the integration in five phases.
Requirement Gathering
We analyzed the client’s business needs in detail, including order processing, inventory management and financial reconciliation.
System Design
We designed the integration architecture, including data mapping between Amazon and NetSuite.
Implementation
We developed the middleware, configured NetSuite to handle Amazon data and set up real-time data synchronization.
Testing
We tested the integration rigorously for data accuracy, reliability and performance under load, including functional, integration and user acceptance testing.
Deployment and Training
We rolled the integration out to the live environment, followed by user training and support.
The project team included a project manager, a business analyst, technical specialists and QA testers, who worked closely with the client to keep the project aligned with its business goals.
Obstacles We Overcame
Marketplace integrations have predictable pressure points. Here’s how we handled each one.
Keeping data consistent
Challenge- Differences in how Amazon and NetSuite structure data risked errors in order processing and inventory management, causing delays and discrepancies.
How we solved it- A thorough data mapping and cleansing process ensured consistent, accurate data flow between the two systems.
Complex integration requirements
- Challenge
- The integration had to handle different shipping methods, multiple currencies, promotional discounts and taxes correctly, which added time and complexity.
- How we solved it
- Custom scripts and business rules handled each scenario, keeping data synchronization accurate and reliable.
Amazon API limits
- Challenge
- Amazon limits how many API requests can be made per minute and which data can be accessed, which could slow syncing during peak sales periods.
- How we solved it
- Middleware with queue management and batch processing made the most of each API call and kept data moving efficiently, even at high traffic.
Protecting NetSuite performance
- Challenge
- Continuous syncing added load to NetSuite, risking slower order processing and other operations.
- How we solved it
- Performance tuning and load balancing let NetSuite handle the extra data without affecting overall system performance.
Security
- Challenge
- Connecting two major platforms meant protecting sensitive customer and financial data.
- How we solved it
- Strong encryption protocols, secure API connections and regular security audits protected all data moving between Amazon and NetSuite.
Change management
- Challenge
- Moving from manual work to automation changed how teams operated, and some users were hesitant.
- How we solved it
- A change management plan with training sessions, user guides and ongoing support helped the team adopt the new system fully.
The Results
The integration paid off across speed, cost, effort and accuracy.
Time Savings- 80%
- faster order processing with automated data transfers
- 90%
- less time spent on inventory management and updates
Cost Savings- 25%
- lower manual entry costs thanks to automation
- 15%
- less excess inventory, reducing storage costs
Effort Reduction- 70%
- less time spent on manual data entry and reconciliation
- 50%
- fewer customer inquiries about order status, thanks to better tracking and updates
Accuracy- 99%
- inventory accuracy rate between Amazon and NetSuite
- 95%
- fewer financial reconciliation errors, with faster period-end closing
Customer Satisfaction: Customer satisfaction scores improved thanks to faster order processing and more accurate stock availability.
Key Takeaways
Inventory sync pays off fastest
Real-time stock updates reduce overselling, stockouts and excess inventory all at once.
Plan for edge cases early
Shipping methods, currencies, discounts and taxes are where marketplace integrations usually break.
Respect API limits
Queueing and batching keep integrations reliable during peak sales.
Automation needs adoption
Training and support turn a working integration into a used one.
