No percentage of revenue or GMV
Zuduno is priced as operations software, not as a share of what your business sells.
Pricing
Pricing shaped around your operation.
Catalogue size and monthly order volume set the commercial baseline. Markets, channels and onboarding scope determine the implementation plan. Users are not metered.
Request a written proposal. We scope the operating model, implementation and commercial terms before you commit.
A commercial model your operations team can explain.
The proposal starts with the size of the catalogue and monthly order volume, then accounts for the markets, channels and migration work in scope. The assumptions and inclusions are written into the proposal.
Commercial principles
Clear scope, predictable terms.
Unlimited users
Catalogue, ecommerce, operations and external collaborators can work from the same context without a per-seat decision.
Channels scoped upfront
The proposal names the channels and integration work included, so implementation expectations are clear on both sides.
Data portability
Your commercial terms include the export and transition conditions needed to keep switching practical.
What shapes the proposal
Five inputs, reviewed before implementation starts.
- Catalogue
- The number of sellable variants, data quality and the product structures that need to be represented.
- Order volume
- The monthly operating range and the exception workflows your team needs to manage.
- Markets
- The countries, locales and market-specific requirements that belong in readiness checks.
- Channels
- The commerce platforms, marketplaces and file-based sources included in the operating model.
- Onboarding
- Source mapping, data validation, parallel running and the sequence for channel activation.
What is included
One platform, one implementation scope.
- Product Master
- Canonical products, variants, identifiers, attributes and channel-specific representations.
- Channel Readiness
- Rule sets, validation workflows and market-specific checks for the agreed channels.
- Inventory & Orders
- Availability, reservations, order intake and operational exception worklists within the agreed scope.
- Migration support
- Source mapping, staged imports, validation and a controlled path to activation.
FAQ
Questions people actually ask
Why is there no public price table?
A useful proposal has to reflect the catalogue, order volume, markets, channels and onboarding work in scope. We prepare the commercial terms after those inputs are reviewed.
Are users metered?
No. Zuduno is designed for cross-functional operations, so the commercial model does not discourage the people who need the information from accessing it.
Can we start with one market or channel?
Yes. The adoption plan can begin with a representative market or the channel that creates the most operational risk, then expand in a controlled sequence.
What do you need to prepare a proposal?
A catalogue size range, monthly order volume, current platforms, target channels and markets, plus the main operational problems you want the implementation to solve.
Get a proposal built around your operation.
Share your catalogue size, order volume, channels and markets. We will turn them into a clear evaluation and implementation scope.