Prepare product rows
Start with product names, codes, units and status fields that match how staff already manage the range.
Product imports must help suppliers prepare products, units, categories, tier prices and margins without pushing unreviewed catalogue data straight into customer ordering.
Rows checked
Categories matched
Tier prices reviewed
Catalogue update ready
Real Porosi product screens. Customers can order on iOS, Android or the web, and submitted orders appear in the supplier dashboard for review.
Wholesale product data affects what buyers can order, what staff can fulfil and what finance later sees. Import workflows must make product and price changes inspectable before the catalogue goes live.
Start with product names, codes, units and status fields that match how staff already manage the range.
Catch missing or mismatched categories before the buyer catalogue becomes hard to navigate.
Inspect tier prices, customer details and margin fields before applying product updates.
Move reviewed data into app and web ordering after staff understand the affected rows.
A buyer builds the order from the products, prices and history available to their account. When they press submit, spreadsheet product setup, product codes, units and categories stay with the order, so the supplier can check it without retyping a call, email or message.
The supplier team receives one order record with spreadsheet product setup, product codes, units and categories. Staff can check exceptions before picking, delivery or invoice preparation begins.
Fast imports can publish product mistakes before anyone notices.
Porosi focuses on reviewed product changes before buyer ordering depends on them.
Customers may struggle when categories, units or statuses are incomplete.
Rows can be reviewed against the catalogue experience buyers will use.
Tier or margin changes may surprise staff later.
Product setup stays close to price and margin context before changes are applied.
Use a realistic product file with new rows, updates, categories, units, tier prices and margin fields.
Choose products that represent normal catalogue complexity, not a tidy demo list.
Check created products, updated products, missing categories and tier-price effects.
Confirm the catalogue will make sense in app and web ordering before broader rollout.
Wholesale product data affects what buyers can order, what staff can fulfil and what finance later sees. Import workflows must make product and price changes inspectable before the catalogue goes live.
Products, units and categories that make sense when they build a basket. Prices and availability context that match their account expectations.
A preview of product rows before customers can order from them. Category and pricing-tier checks that expose setup problems early.
Use a realistic product file with new rows, updates, categories, units, tier prices and margin fields.
Bring a product spreadsheet, price-tier examples and the catalogue problems staff currently repair by hand.