Log in
FRENG

Who it's for

Written for caterers, useful to everyone who organises.

The vocabulary changes, the mechanics do not.

Event caterers

Kitchen, delivery, service, breakdown. This is the trade PRESTKA was written for: there is nothing to translate.

  • The run sheet writes itself once the date is set
  • Extras accept by text, without an account
  • The master calendar holds the whole house

Agencies and wedding planners

You do not cook, you coordinate. The job is no longer the kitchen but the address book: finding the right people, holding a schedule that keeps moving, knowing at any moment who has confirmed.

  • Booking follow-up moves to the centre
  • The directory takes over: profiles, groups, clients, rooms
  • Production columns stay available, without imposing themselves

Companies organising in-house

Offsites, general meetings, client evenings. When events are an internal service, the buyer is no longer an owner but a manager, and the question becomes the framework.

  • Published in France, one database per client
  • Reversibility is written into the contract
  • Written answers for your DPO and IT department

What we get asked

The four questions that keep coming back.

  • Our suppliers are not our employees.

    A booking is an offer, not an employment contract. The extra accepts from a link, without an account, and nothing is assumed about their relationship with you.

  • The vocabulary is too kitchen-focused.

    Production columns only appear if you use them. What you do not need is not shown.

  • Where is the data hosted?

    In France. The code is owned by the publisher, and every client gets their own database, not a slot inside a shared one.

  • How do we get our data back if we leave?

    Export on request, deletion within thirty days. Reversibility is in the contract, not negotiated on the way out.

BONJOURHELLO

Loading0%

Loading the site