Packages
Set up your prepaid service packages so Nabu can correctly track upfront payments and per-session redemption values.
What are packages?
A package is when a client pays upfront for a bundle of future sessions — for example, $500 for 5 HydraFacials, or $900 for 6 laser hair removal sessions. They get a discount compared to paying per session, and you get guaranteed revenue and client commitment.
From an accounting standpoint, packages work like this: you collect cash today, but deliver the service over time. Each time the client redeems a session, that session's portion of the original payment gets recognized as revenue.
Packages vs. memberships
| Packages | Memberships | |
|---|---|---|
| Payment | One-time upfront | Recurring monthly |
| Session count | Fixed — they run out | Ongoing until cancelled |
| When revenue is recognized | Per redemption | Per monthly payment + redemption |
Both are prepaid. The key difference: packages have a finite number of sessions that get used up. Memberships are subscriptions that renew every month.
Fields
| Field | What to enter |
|---|---|
| Package name | Use the exact name from your booking software (e.g., "Laser Hair Removal 6-Pack") |
| Service | Which service this package is for |
| Sessions included | Total number of sessions in the package |
| Package price | What the client pays when they buy the package |
| Status | Active or Inactive |
The package name should match your booking software so Nabu can link package purchase and redemption records from your sales history to the right definition here.
Per-session value
Nabu divides the package price evenly across all sessions by default.
Example: A $500 / 5-session HydraFacial package = $100 attributed per redemption.
That per-session value ($100) is what Nabu uses when calculating how much revenue a session generates. If the single-session price is $150, a package redemption generates less revenue per appointment — which is worth knowing when analyzing your service mix.
How packages appear in sales data
When you import Sales & Visit History, package transactions appear as:
- PACKAGE_SALE — when a client buys the package (full $500 collected)
- PACKAGE_REDEMPTION — when a client uses a session from that package
Nabu matches these to the package definitions you set up here. Unmatched package records will be flagged for review.
Existing package balances
If clients already have unused package sessions (from before you started using Nabu), those should come in through the Sales & Visit History import. You don't need to manually enter existing balances here — this section is only for defining the packages themselves.
Confirming this section
If you don't sell packages, mark this section as Not Applicable. If you plan to add packages later, you can set them up when you launch them.
Common questions
What if clients have leftover sessions from a package they bought years ago? Those appear in the historical sales import as PACKAGE_REDEMPTION records. Nabu will track them against the correct package if the package is defined here.
Can a package include multiple different services? Nabu's current package setup links one package to one primary service. If you sell a multi-service bundle (e.g., 2 facials + 1 peel), enter it with the main service and a note. Reach out through Help in the sidebar if you need more complex package structures.
What if the package price doesn't divide evenly across sessions? Nabu rounds to the nearest cent. For example, $100 for 3 sessions = $33.33 per redemption (with one session carrying $33.34 due to rounding).