Retail, commerce and marketplaces: the operating job, and how a first project is scoped

Current pressures

Pressures operators describe in this sector in 2026. Each is a failure mode, not a call to modernise.

The workflows a project touches

A first project cuts into this sequence. Scope which steps it owns before choosing software.

1. Product data intake. Items arrive from suppliers, a bulk file or an internal team, and are normalised into one shape with required attributes, variants and media.
2. Channel publication. The normalised item is mapped to each channel's taxonomy and attribute rules, published, and monitored for rejection.
3. Availability. One figure per item per location, with reservations, in-flight returns and supplier lead times represented, not assumed.
4. Order capture. Orders from every channel are normalised into one record with a single identifier the customer can be told.
5. Fulfilment. Allocation, picking, dispatch and the delivery promise, including when it cannot be kept.
6. Returns and refunds. The reverse path, with stock, payment and supplier claim updated from one event.
7. Customer contact. Order status, returns and product questions, routed with the order record attached.
8. Reconciliation and reporting. Channel settlements, fees and adjustments matched against orders, with the difference explained, not absorbed.

Steps 1 to 3, and the trust mechanics around independent sellers, are detailed in marketplace and classifieds operations. Steps 3, 5 and 8 are back-office mechanics, in ERP and back-office operations. Step 7 is customer support automation.

Data and regulatory constraints

Settle these before the architecture, because each one changes the data model rather than the feature list.

• Shopper personal data. Consent, retention and deletion apply to the customer record, the order history and the marketing identifiers attached to both. Decide the retention period per market before the first table is designed.
• Payment card data stays with the payment provider. Your application holds a token and a reference, never the card. That is a boundary decision, not an optimisation.
• Tax and invoicing differ per market. The order record must carry the rule in force at the moment of sale, because a later correction is judged against that moment.
• Channel terms restrict what you may store and export. A marketplace agreement often limits retention of buyer contact data and forbids re-use. Read it before designing a customer master.

The usual integrations are channel and marketplace APIs, a payment provider, a shipping aggregator, a search index, an accounting or ERP system, and analytics. Each needs a named owner, a sandbox and a defined behaviour when it fails.

Where a first project starts

OutsourcingVN follows one delivery lifecycle: discovery and strategic alignment; team assembly and architecture planning; agile execution with outcome-based milestones; modular components; training and rollout; ongoing support.

1. Count the real volume. Items, variants, channels, orders per peak day, returns and contacts per week. Bring the numbers you have; estimates are marked as estimates.
2. Name the owner of each record. Catalogue, availability, order, customer. Where two systems own one record today, that conflict is the project.
3. Pick one channel and one category for a first milestone, with written acceptance criteria.
4. Build the normalised record before the integrations. A connector built onto an undefined catalogue has to be rebuilt.
5. Run the reverse path in the pilot. A pilot that tests only the forward order path proves the easy half.
6. Widen by channel, then by category, against the measures baselined in step one.

Most projects are agreed as fixed-scope contracts after discovery. Milestone acceptance is described on the project delivery page, and how evidence is labelled on the methodology page. The commercial route for this sector is custom product engineering; other engagement shapes are listed under services.

What delivery record exists, and what does not

Netbase has served more than 500 clients; no project or country counter is published. Clients are in the United States, Europe and Asia-Pacific, and most projects come from clients outside Vietnam. Those are service markets, not office locations.

Netbase began with e-commerce products and solutions, delivered e-commerce projects between 2013 and 2015, and added consulting and outsourcing services in 2016. That is company origin, not a current sector claim.

One anonymised record in this sector is published in full. For a founder who is not named, Netbase delivered a bilingual classifieds platform: requirements, design, a Laravel backend with REST APIs, one-time-password accounts, paid ads, search, ratings, messaging, event ticket ads, a blog and forum, payments, multi-language SEO and AWS deployment. It ran in six milestones over four months, with training and six months of support. No result or traffic figure is claimed. The full record with its evidence limits is the classifieds platform with AI-assisted moderation page; every published record is listed under work.

Beyond that record, OutsourcingVN publishes no delivered project record for a named retail chain, commerce brand or marketplace operator. The case for a first project rests on the workflow overlap above and on the delivery method, not on an implied sector track record.