Orders and fulfilment
Store orders, marketplace orders, returns and PO returns share one workspace. Filter by store, order status or procurement status, and read amounts, SKUs, tracking and order time on a single row.
Built for Walmart, SHEIN, TEMU and Amazon sellers
Marketplaces differ. Your records should not.
Mainsail ERP connects sourcing, bulk listing, fulfilment and procurement reconciliation, so operations, buyers and finance work from one set of records.
Each marketplace, modelled on its own terms.
Listing fields, price review and shipping semantics are modelled per platform, so operators stop switching between seller back offices.
WalmartListing and fulfilment
- Pending and live listing management
- Bulk publish, repricing and stock edits
- Order sync and tracking write-back
SHEINListing and price review
- Pending and price-review queues
- Live listing editor with category hints
- Warehouse and logistics orders
TEMUSemi-managed
- Pending listings and price control
- Live listings and purchase orders
- Shipment orders and tracking
AmazonSourcing and monitoring
- ASIN capture and monitoring logs
- AI sourcing library and product library
- UPC and identifier management
How it works
From capture to settlement, the trail is unbroken.
These are not four separate tools. Each stage hands its result to the next one, on the same record.
01
Source
Products captured from Amazon land in the sourcing library. AI retouching produces listing images, and blacklist rules block risky items before they move on.
- AI sourcing library
- Product blacklist
- Image space
02
List
Pending products are organised per platform. Bulk repricing, stock edits and publish queues run in the background, with review results returning to the same view.
- Pending queue
- Task queue
- Live listings
03
Fulfil
Store and marketplace orders arrive in one workspace, where procurement status, tracking numbers, returns and refunds stay attached to the order.
- Store orders
- PO returns
- Refunds
04
Settle
Order settlement and procurement statements are generated per cycle. Approver, timestamp and amount differences are all recorded and exportable.
- Settlement
- Statements
- Reimbursement
Five modules, shaped around what cross-border teams actually do all day.
The split follows real roles: operators watch listings and orders, buyers watch supply and statements, finance watches settlement, risk watches infringement.
Procurement and reconciliation
Warehouse purchase confirmation, supplier quotes, PO returns and statements move along one line. Every statement records the receivable, the settled amount, the approver and the timestamp.
- Purchase confirmation and rejection
- Statement generation and download
- Reimbursement and credit ledger
Products and publishing
Pending, in review, published and rejected listings live in separate tabs, while bulk repricing and publish queues run in parallel.
Trademark patrol
TRO detection sweeps live listings in batches. Title risk, image risk and matched keywords produce a risk score, with takedown available inline.
AI and add-ons
AI retouching bills by credits, the risk engine flags exposure, and ASIN monitoring plus scheduled patrols keep running in the background.
- AI retouching
- Bulk white-background and lifestyle images
- Risk engine
- Compliance and operational risk signals
- ASIN monitoring
- Change history on your own and competing listings
Get sourcing right and the rest of the pipeline stops backtracking.
The sourcing library puts capture environment, source store, category, rating, review count, capture price and marked-up price on one table, so the decision happens before anything is pushed to a store.
Captured straight into the library
Products captured by the client land in your organisation library, viewable by platform or by store.
Retouch before listing
AI retouching produces white-background and lifestyle images, billed by credits, with output volume set in your retouch settings.
Push to pending in bulk
Select rows and move them into a target store queue, carrying size and category attributes along.
Security and governance
Multi-tenant by design, not by convention.
Data is scoped by organisation at the query layer, identity comes from the signed token rather than the request body, and every sensitive action leaves a record.
- Organisation isolation
- Every query is bound to the organisation, and store ownership is verified before order data is returned.
- Role-based access
- Menus and actions follow role. Settlement, member management and finance views are restricted to the roles that own them.
- Operation logs
- Logins, edits and bulk operations are written to an operation log that administrators can search.
What onboarding looks like
Most teams go live on the first marketplace within a few weeks, then add platforms one at a time.
- 01
Connect stores
Authorise marketplace accounts and import existing listings and orders.
- 02
Map your process
Set roles, approval steps, price rules and blacklist rules to match how your team already works.
- 03
Run one platform
Go live on a single marketplace, verify listings, orders and statements end to end.
- 04
Scale out
Add the remaining platforms and stores, then turn on patrol and monitoring add-ons.
Tell us how your team runs today.
Share your platforms, store count and where the process breaks. We will walk you through the parts of Mainsail ERP that apply.