Configure products, customer accounts, pricing, ordering, fulfilment and finance in the order they depend on one another.
Porosi works as one connected system, so configuration should follow the same direction as a real wholesale order.
Brand, workspace, staff access and implementation owner.
Use one clean product model before assigning customer prices.
Account access, catalogue visibility, pricing and delivery context.
Supplier-branded web ordering, iOS and Android share the account model.
Decide where staff control exceptions and what can run automatically.
Create, amend and reconcile one test order before go-live.
Showing all 24 documentation references.
Workspace, people and customer access
Prepare the workspace, brand and implementation owner.
Give staff the access their operational role requires.
Connect customer users to the correct trade account.
Catalogue structure and commercial context
Maintain the customer-visible catalogue and its commercial rules.
Define the product record buyers and operations rely on.
Prepare and validate structured catalogue data before launch.
Trace visibility and price back to the selected customer account.
Supplier-branded web and mobile journeys
Understand the customer path from account access to submission.
Use the same account and catalogue context across every channel.
Understand which operational rules shape checkout.
Keep the customer action connected to the supplier workflow.
Review, pick, stock, delivery and reporting
Follow a submitted order through the supplier dashboard.
Keep staff decisions attached to the same order record.
Connect fulfilment to the delivery context your team uses.
Choose output based on the operational question.
Understand the boundary between operational stock and finance.
Invoices, accounting handoff and corrections
Read the invoice state from the connected order context.
Follow the finance handoff without losing the Porosi order.
Use the exact validation result and source order to diagnose a failure.
Review the current integration position before planning a handoff.
White-label release and approved system access
Prepare supplier identity, customer access and release ownership.
Verify the same supported workflow across each customer channel.
Agree the purpose, scope and validation plan before credentials are issued.
Define system ownership and the records that cross the boundary.
Select an object to see what it owns, what controls it and what it passes into the next stage.
The commercial identity behind access, catalogue visibility, pricing and delivery context.
Product data describes what can be sold. Customer records determine who can see it and which commercial price applies.
Name, category, image, unit, tax treatment and availability.
Base price, pricing tier or a customer-specific override.
The selected account determines the catalogue and price shown.
Review catalogue records before assigning customer pricing.
Each team works from the shared order record instead of rebuilding it at every handoff.
Porosi can automatically accept incoming orders and send picking slips to a connected printer as orders arrive. Staff still work from the same order when an exception needs attention.
Read the picking workflowIf an invoiced order changes, Porosi can update the connected Xero invoice rather than forcing your team to rebuild the order or maintain a separate correction record.
Read the invoice workflowPorosi carries the wholesale order and its operational amendments. Accounting integrations receive the finance record without replacing the order workflow.
Users enter through a supplier relationship and an approved customer account.
The selected account keeps products and commercial rules attached.
Operational decisions remain on the source order through fulfilment.
Porosi controls the order context; Xero receives and updates the accounting invoice.
The accounting platform remains the finance system of record.
API or ERP access follows an agreed scope and validation plan.
Prepare the app-store identity, customer access and integration boundary as one controlled release.
Supplier name, icon, colours and customer-facing domain.
App identifiers, listing information and release ownership.
Approved customer account, catalogue, pricing and ordering checks.
Confirm supported ordering behaviour on web, iOS and Android.
Porosi API access is not self-serve. Contact us with the system, purpose, records and expected direction of data before an interface is approved.
Request API permissionUse a representative customer account and follow the same order through the customer channel, supplier team, fulfilment and finance handoff.
