Matchbox Neto Marketplace Integration
SDLC Corp developed custom Node.js middleware so Matchbox could connect its Neto commerce system with multiple marketplace APIs. In addition, the integration handles product listings, inventory updates, marketplace orders and dispatch tracking in one connected process.

The ProjectAt A Glance
Overall, Matchbox’s project brought its central commerce records and marketplace workflows together.
KG Electronics (Matchbox)
Namely, an ecommerce retailer managing product and order information across multiple sales channels.
Neto
Specifically, the central system for products, inventory, orders and dispatch records.
Node.js And MongoDB
Node.js and Express handled connectors, while MongoDB supported transaction records.
SDLC Corp
Overall, custom connector development and integration architecture.

One Neto Catalogue,Multiple Channels
Matchbox managed its catalogue, stock and orders in Neto while selling through multiple marketplaces. However, each channel used its own listing and order format. We kept Neto at the centre of the integration so the team could work with familiar records.
We preserved marketplace order references during import to support fulfilment and reconciliation. Therefore, we never treated an order from one channel as an unrelated transaction.
We also considered repeat submissions and missing acknowledgements when defining the order flow. Those checks were important because a failed API response does not always mean the original order was rejected.
Multichannel SellingProblems To Solve
Matchbox faced a familiar multichannel problem, because one product or order could appear differently on each marketplace. So we had to account for differences in required fields, update timing and order references.
Listing Formats
First, marketplaces require different category, variant and product attributes.
Stock Accuracy
Second, a stock change in Neto needs a matching update in the seller channel.
Order Handling
Third, imported orders need their original channel IDs for reliable reconciliation.
Dispatch Updates
Next, tracking data must match the correct external order after fulfilment.
Pricing Rules
Similarly, price and offer fields may differ between marketplace APIs.
Failure Visibility
Finally, failed requests and missed acknowledgements must be easy to investigate.
Connectors BuiltAround Neto
So we built a middleware layer to separate Neto's data model from each marketplace's API requirements. Shared processing handled common tasks, while individual connectors dealt with channel-specific fields. Explore our software integration services.
Plan A Similar IntegrationNeto ERP
In short, the central source for catalogue, stock and order data.
Custom MiddlewareProcessing Layer
Meanwhile, shared processing coordinated validation, routing and API requests.
Marketplace APIsSales Channels
Likewise, channel adapters translated platform-specific records.
Scheduled Jobs
In addition, scheduled tasks triggered regular updates without manual exports.
Sync History
Besides that, transaction references supported checks and follow-up investigation.
Failure Alerts
Equally, failure notifications highlighted requests that needed attention.
Data MovementAcross The Connector
Overall, we connected four data movements between Neto and the sales channels. Moreover, each had a defined direction and a distinct record to check.
Automate Your Marketplace WorkflowProduct Listings
First, we converted product fields and variations into each channel’s listing structure.
Stock Updates
Second, we sent stock and offer changes from Neto to the marketplace API.
Order Import
Third, we brought orders into Neto and retained external order IDs for reconciliation.
Tracking Return
Finally, we matched carrier and tracking data with the originating marketplace order.
Technology Stack & Architecture
Specifically, Node.js and Express powered the API-handling layer. MongoDB held synchronization references, while scheduling, HTTP-request and email utilities supported routine jobs and failure notifications.
- Runtime: Node.js · Express · JavaScript. Namely, Express apps host API routes, marketplace requests and channel-specific rules.
- Data & Jobs: MongoDB · Mongoose ODM · node-schedule. Meanwhile, this layer stores offers, orders, products, sync history, snapshots and job references.
- API & Alerts: Axios · Nodemailer · CSV / JSON snapshots. Together with those, HTTP requests, diagnostic records and alerts supported troubleshooting.
Marketplace ChannelsIn Scope
Altogether, the Matchbox scope named eight marketplaces. We designed channel-specific handling for listing fields, order formats and fulfilment data while keeping the Neto integration consistent.

Altogether, the marketplaces included in the Matchbox integration scope
Integration DeliveryFor Matchbox
Overall, our work connected the key marketplace workflows with Neto. These deliverables describe integration capabilities rather than unverified traffic or revenue gains.
Scheduled Data Exchange
First, we added scheduled flows for selected catalogue and inventory updates.
Stock Update Routing
Second, we routed inventory changes from Neto to the relevant channel endpoints.
Marketplace Order Import
Third, we retained marketplace identifiers when bringing order records into Neto.
Dispatch Status Return
Finally, we mapped dispatch information back to the corresponding external orders.
Engineering Decisions Behind The Integration
So we made three design decisions to keep Neto and marketplace workflows manageable.
01. Channel Mapping
First, we kept marketplace-specific field mapping inside its connector. Consequently, Neto product and order records stayed consistent.
02. Data Validation
We retained external order references and checked incoming records before import. Hence, we gained a way to recognize repeat requests.
03. Operational Visibility
Third, we recorded sync activity and exposed failures for follow-up. Thus, exceptions became easier to trace than a silent background job.
Channel-specific mapping: For example, eBay and Bunnings can require different product attributes. Therefore, we kept those mapping rules separate.
Planning a similar integration? Then explore software integration services, see ecommerce development capabilities, or discuss your marketplace connector requirements.
Planning AMarketplace Integration?
Need to connect your commerce system with marketplaces? First, tell us your channels and order workflow. Then we can scope the integration and testing with you.
Discuss Your Integration
- Contact Us
Let’s Talk About Your Product
What happens next?
- We review your requirements
- Strategy call with experts
- Clear roadmap & estimate
- NDA Protected
- Enterprise Grade Delivery
- Global Clients





