Sales Channels
Connecting Jochen Schweizer
Sell experiences through Jochen Schweizer and mydays: store the token, link the offer with Experience and Location, transfer dates, understand bookings and credit notes.
How the connection works
Jochen Schweizer mydays (JSMD) sells your experiences as vouchers. The guest redeems the voucher in the Jochen-Schweizer-Erlebnisportal (JEP) and chooses a date there. For this, Unitlify transfers your dates with capacity to the portal, and the portal reports every redemption back to Unitlify as a booking.
Unlike GetYourGuide, Jochen Schweizer does not ask for free places live. The portal works with the transferred dates and manages the capacity there itself. What this means for you is explained under "Dates and capacity".
Requirements
- A partner account at Jochen Schweizer mydays with access to the experience portal.
- Your Product Supplier Token from the portal.
- The experience is created in the portal (Experience) and assigned to a location (Location).
- The matching offer in Unitlify is active, with dates whose duration corresponds to the experience duration in the portal.
Step by step
1. Store the token
Menu Booking system → Sales channels, row Jochen Schweizer, Manage. Enter the Product Supplier Token and save. Unitlify tests the connection immediately; if the test fails, nothing is saved. The token is stored encrypted and afterwards only shown masked. With Test you can check the connection at any time, with Remove you disconnect it.
2. Switch the channel on
The toggle in the channel row is active after connecting. If you set it to inactive, Unitlify stops sending new dates to the portal. Dates already in the portal remain bookable, and redemptions from the portal are still accepted so that vouchers already sold are not lost.
3. Link the offer
Expand the offer in the product list. Select the JSMD Experience and then the Location from the data of your portal and click Link. Unitlify stores its identifiers in the portal so that both systems refer to the same experience. The list then shows "linked" and the name of the experience from the portal is saved.
Exactly one Experience is possible per offer. Offers "bookable by businesses and institutions only" cannot be linked.
4. Material number (only with several offers per location)
Jochen Schweizer reports bookings with an SAP material number. Unitlify assigns a booking as follows: first via the material number, otherwise via the location, if exactly one active offer is linked there. If you have several offers at the same location, enter the JS material number (SAP) from the portal for each of them. Otherwise Unitlify cannot assign the booking to any offer, and it is lost.
If a location has only one offer, Unitlify automatically remembers the material number with the first booking.
Dates and capacity
What is transferred
- New time slots, including those generated automatically from the validity, are sent to the portal with start time, duration and total capacity. The booking cut-off in the portal is fixed at 2 hours before start.
- Changes to the capacity or duration of a time slot are carried over.
- Deleted time slots are deleted in the portal.
- After a change of the validity (periods, weekdays, exceptions), Unitlify synchronises all dates: new ones are created, dropped and blocked ones are deleted in the portal.
No dates are transferred during the linking itself. The dates are in the portal as soon as new time slots are created or you save the validity of the offer. So after linking, check the validity and save it once, then all dates are over there.
What is not transferred
- Bookings from the shop, widget, GetYourGuide or administration do not reduce the capacity in the portal. The portal only knows the total capacity per time slot and deducts only its own redemptions. If you sell the same date through several channels, Jochen Schweizer can therefore allocate more places than are free on your side. Unitlify accepts the booking anyway and warns your team by push notification if a resource is overbooked as a result.
- Manually blocked time slots remain bookable in the portal, because only capacity and duration are sent. To block a date at Jochen Schweizer as well, set the day capacity to 0 or use a resource closure of the type "Closed", see Capacity and resources.
- Weekday rules and prices apply only to your own shop.
Recommendation: give Jochen Schweizer its own time slots or its own quota (for instance via a separate price list or a separate date) instead of selling the same scarce date through all channels.
The duration must match
For a redemption, Unitlify looks for the time slot with exactly the same start and end time. If the experience duration in the portal differs from the duration of your time slots, Unitlify finds no time slot and creates its own one with a very large capacity for the booking. In the time slot overview this looks like an additional date. Keep the duration the same in both systems.
Bookings
Every redemption in the portal appears in Unitlify as a confirmed booking with the channel badge JSMD:
- Name: the name of the experience from the portal plus your category, for example "High Swing Berlin Basic · for 1 person".
- Participants: one participant per redeemed voucher. The voucher code is stored as the ticket code on the participant.
- Amount: the price reported by the portal. If it is missing, the price of your main category. The final remuneration comes with the settlement credit note (below).
- Note: order number, experience, brand (Jochen Schweizer or mydays), sales source and voucher codes.
- Emails: Unitlify does not send the guest a booking confirmation, the portal does that.
- Places: a redemption occupies one place in the time slot; in resources it counts with its number of persons.
Cancellations and rebookings run exclusively through the portal. In Unitlify, "Cancel" and rebooking are locked for JSMD bookings.
Credit notes and payout
Jochen Schweizer reports two kinds of credit notes:
- Cancellation: the guest has cancelled the redemption. Unitlify sets the booking to cancelled and releases the places.
- Settlement credit note: your remuneration for a redeemed booking. Unitlify stores the amount on the booking; if the amount was previously 0 €, it becomes the booking amount. With the payout notification from the portal, the credit notes are assigned to the payout.
The settlement itself runs through Jochen Schweizer, Unitlify only shows the reported amounts.
Troubleshooting checklist
- Booking from the portal does not appear in Unitlify: several offers at the location without a material number, or the offer is not active. Enter the material number.
- Additional date with large capacity in the overview: the duration of the time slot and the experience do not match.
- Dates are missing in the portal: no validity saved after linking, or the time slots were created before the linking. Save the validity once.
- Blocked date was booked through Jochen Schweizer: blocks are not transferred. Use day capacity 0 or the resource closure "Closed".
- Overbooking: the same date was sold through the shop and the portal. Separate the quotas.
- Booking shows 0 €: the portal did not report a price and the main category has no price. The amount is added with the settlement credit note.
Still have questions?
Our team is happy to help you with the setup.
