Automated
The order triggers provider automation and the service appears without manual intervention.
- Order
- script / plugin
- service created
Marketplace · Custom
If a provider can describe the service, the catalogue does not have to stop at servers.
Custom listings are provider-defined offerings: order forms, approvals, provider-defined components and the same lease and settlement guarantees as any other product.
- 01 Custom offering
- 02 Order form
- 03 Provider approval / automation
- 04 Fulfilment
- 05 Metered or fixed component
- 06 Settlement
Fulfilment follows the provider's mechanism. The agreement and the money stay verifiable.
Range
What providers list as custom offerings
- consultancy hours
- support desk
- implementation package
- training credit
- data-processing job
- software licence
- remote catalogue item
- scripted automation
- specialised managed service
Custom
Illustrative exampleInfrastructure Migration Package
Example Provider
Remote delivery
- 20 engineering hours
- Project approval required
- Fixed scope
Fixed-fee package
Custom
Illustrative exampleScripted Data Processing Run
Example Provider
Provider-defined
- Custom order form
- Output to object storage
Provider quote
Managed
Illustrative exampleTraining Credits
Example Provider
Remote or on-site
- Credit block
- Scheduled sessions
Prepaid block
Anatomy
Anatomy of a custom offering
Twelve fields a provider defines. Not every field is required for every listing — but each one has a place.
- Title
the product name the provider defines
- Category
where the offering sits — custom, or a category the provider maps it to
- Provider
the organisation that fulfils and supports it
- Description
what is delivered, in the provider's own terms
- Plan
the purchasable variant and its pricing basis
- Components
how the engagement is measured or billed
- Order fields
extra information collected before fulfilment
- Limits
caps on components or scope
- Approval rules
whether a provider sign-off precedes fulfilment
- Backend
the script, plugin, entitlement system or team that delivers
- Lifecycle actions
what can be changed, paused or ended
- Usage model
metered, fixed or mixed
Fulfilment
Fulfilment patterns
Provider-approved
A provider review step precedes fulfilment — useful for scoped or high-touch work.
- Order
- approval
- service fulfilment
Entitlement
Fulfilment changes an entitlement rather than deploying infrastructure.
- Order
- account / seat / licence
- access activated
Metered service
Consumption is measured and settles per component against the lease.
- Order
- usage component
- settlement
Human service
People deliver the work; the catalogue and settlement rail keep the engagement accountable.
- Order
- approved work allocation
- billable component
Verify before you rely on a mechanism. The offering model supports these patterns, but
what a given provider deployment can actually fulfil depends on its Waldur configuration, plugins,
credentials and deployment certification. An integration present in upstream Waldur is not automatically a
certified VirtEngine adapter.
Managed services
Managed & professional services
Human and managed services sold through the same catalogue: consultancy, implementation, support, managed operations and training.
Why list professional services here?
The same problems apply as for infrastructure: who is the counterparty, what was agreed, what was delivered, and when does money move. The catalogue and settlement rail answer them without a separate procurement system.
What stays with the provider
Scoping, delivery, quality and support. The protocol makes the engagement orderable and the payment conditional on agreed components — it does not perform the work.
Technical detail
Under the hood
Verify it: fulfilment patterns above for the fulfilment patterns, Waldur integration for custom offering types and approval workflows, and Waldur's marketplace model for the upstream offering structure.
Continue