Part of mPorts OMS
One product record, ready for the places you sell.
Products & catalog in mPorts OMS keeps one record per item — images, categories, attributes, variants, suppliers and cost, and the identifier each retailer uses for it — and lets you import and export the whole catalog as a spreadsheet. It is the product data your launches, orders, inventory and reports all work from.
The same product, described five different ways
Home Depot wants an OMSID. Lowe’s wants an item number. Every other retailer wants its own identifier, and your warehouse wants yours. When each of those lives in a different spreadsheet, every update to a product becomes a hunt for which copy is right.
mPorts OMS keeps one record and hangs every retailer’s identifier off it, so an update is made once and the launch, the order and the report all read the same product.
Every product, in one list
The Products screen: search by SKU or name, filter by status, see stock, listings and catalog status per product, and import or export the catalog.
One missing identifier, caught before it blocks an update
A retailer update for a product fails because that retailer’s identifier was never recorded.
-
Signal
The Retailer IDs view lists the product under “Needs attention”: a required identifier for one retailer is missing.
-
What mPorts shows
The product record, the identifiers already mapped for other retailers, and which one is empty.
-
Action
The operator adds the identifier once, on the product.
-
Record
The change is recorded on the product; the next update to that retailer carries the right identifier.
-
One record per product
Images, categories, attributes, variants, suppliers and cost, per-channel listings.
-
Import and export
Download the catalog as a spreadsheet, edit it, and upload it back to create or update products in bulk.
-
Review-first import mapping
Map a supplier’s workbook to your fields once, review what will change, and keep the mapping for next time.
-
Retailer identifiers
The identifier each retailer uses for the product, with a view of the ones that are missing.
-
Categories and attributes
Your own categories, and the attribute definitions launches and listings draw from.
-
Catalog status
Whether each product’s live listings are clean, in error, pending or not yet launched, re-checked from the connected channel.
Two catalogs, two jobs
This is the operational product data behind the channels you sell on, and getting products ready for them. mPorts Distribution has a catalog of its own: the one your suppliers list into and your business buyers shop from, on your own marketplace. A company can use one without the other.
What a retailer requires before a product can go live
Beyond what mPorts manages, each retailer sets its own requirements — accurate attributes and images, its own identifiers, its own category mapping and, for regulated goods, its own compliance documentation — before it will accept a new item.
What is catalog readiness, and what do retailers require?Questions buyers ask
How does product data work inside mPorts OMS?
One record per item — images, categories, attributes, variants, suppliers, cost and each retailer’s identifier — imported and exported as a spreadsheet, with per-channel listings on top. It is the product data every order, launch and report in mPorts OMS runs on, and it works alongside a product information system you already run.
Can I bring products in from a supplier’s spreadsheet?
Yes. Upload the workbook, map its columns to your fields, review exactly what will be created or changed, and commit. The mapping is kept so the next file from that supplier takes minutes.
Does the AI organise or classify products for us?
There are AI-assisted suggestions for import columns and for organising products, and both are review-and-approve: a person accepts each suggestion. Whether they are enabled for your account is confirmed during onboarding.