Skip to main content
A bundle keeps two or more Journey services together as one package. Each service still keeps its own pricing, supplier, dates, and operational details, while you control how the package is presented to the client.

Single bundle card

The default for new bundles. The client sees one curated package card with one combined amount.

Main service + attached services

The client sees the main service and each visible attached service with its own price.

Two Ways To Create A Bundle

In the Library (reusable)

Build the bundle once, then add the same package to any Journey. Covered below.

On a Journey (one-off)

Bundle services that are already on a Journey. See the Journey Builder guide.

Create a reusable bundle in the Library

Use a Library bundle when you want to add the same package to multiple Journeys.
1

Start a new bundle

Open Library → Templates & Bundles, then select New bundle.
2

Add and arrange services

Add at least two Library services, put them in the order you want, and choose the main service.
3

Add the client-facing details

Give the bundle a title. You can also add an optional description and cover photo, then save it.
4

Add it to a Journey

In the Journey Builder, open Add to journey → Templates & Bundles and select the bundle. Odia creates a new Journey copy, so later Journey edits do not change the Library bundle.

Choose what the client sees

A bundle can present itself to the client in one of two ways. Switch between them from the bundle’s Client presentation control — see the Journey Builder guide for how to change it and edit members.

Single bundle card

This is the default for every new bundle. Use it when the services make up one package that should have a clear name and combined amount.
  • The client sees one package card with the bundle title, description, and cover photo.
  • Visible member services appear as the package inclusions.
  • Individual member prices are not shown on the public Journey.

Main service + attached services

Use this when the main service should lead the group but the client still needs to see each attached service and its price.
  • The main service appears as the main card.
  • Each visible attached service appears beneath it with its own price.
  • The services stay grouped together in the Journey Builder.
For a newly created package, keep Single bundle card unless the client needs to review the attached services as separate priced items.

Understand the bundle amount

A bundle does not have a separate package price. Its customer amount is calculated from the eligible member services:
  • Each member service keeps its own price, cost, supplier, commission, and margin.
  • Eligible member amounts are converted with the Journey’s exchange rates before they are combined.
  • A hidden member still contributes to the combined amount.
  • A client-direct service does not add a customer amount because the client pays the supplier directly.
  • Selected add-ons are added separately to the Journey total.
Hiding a service changes what the client sees; it does not change the bundle amount. To change the amount, edit the member service’s pricing or use Remove from group on that member service.

Bundles on invoices

When a customer invoice includes a single-card bundle, Odia can save it as one package line with the bundle title and combined eligible amount. Supplier invoices remain itemized by member service. Issued invoices keep the bundle wording and amount saved on the invoice, so later Journey edits do not silently change them. See Bundles on Invoices for the complete invoice behavior.

Bundle or template?

Templates

Compare a bundle against a template, and learn how to create a template instead when the services should stay independent.

Troubleshooting

Hidden services still contribute to the bundle amount. Open each member’s pricing to review its customer amount, and check whether any selected add-ons are adding separately to the Journey total.

Journey Builder Guide

For creation-selection and editing issues (grouping, main service, presentation mode), see the Journey Builder guide.