Pre-orders with a deposit
Customers reserve a cake, a catering order or a table and pay a deposit in the app with card, KakaoPay, NaverPay or Toss. You see every pre-order on one page, with the deposit already in.
The problem this solves
Big orders taken by phone or chat get lost, and a no-show on a custom cake costs real money. Taking a deposit when the order is placed makes the order real, and keeping orders in one list means nothing is missed.
What you end up with
A pre-order form on your site: pick the item, the pickup day and time, add notes, and pay the deposit. The customer gets a confirmation; you get the order on a page only you and your staff can open, sorted by pickup time.
How it works
- A customer picks what they want and a pickup day and time, and adds notes.
- They pay the deposit in the app with card, KakaoPay, NaverPay or Toss.
- They get a confirmation email; the payment receipt comes from DontCode on its own.
- The pre-order lands on a staff page, sorted by pickup time.
- Days you're full or closed can't be picked.
Build this in your app
Build this in your appInsight asks a few questions first, so it fits your app.
Built from
Card payments
PaymentsYour customers can pay by card right in your app's checkout, once or on a subscription that renews on its own. Price in won or US dollars. DontCode handles the security and confirmations; you add your payout account, and payments open once DontCode turns them on for your app.
KakaoPay
PaymentsKakaoPay is built into your app's checkout, next to card, NaverPay and Toss Pay. Your customers choose it when they pay; DontCode handles the merchant setup, security keys, and payment confirmations. There's no payment code to write and no keys to manage: add your payout account, and payments open once DontCode turns them on for your app.
NaverPay
PaymentsNaverPay is built into your app's checkout. Your customers choose it when they pay, and DontCode handles the rest. Add your payout account; payments open once DontCode turns them on for your app.
Toss Pay
PaymentsToss Pay is built into your app's checkout. Your customers choose it when they pay, and DontCode handles the rest. Add your payout account; payments open once DontCode turns them on for your app.
Forms
App servicesNeed a contact form, a booking form or a survey? Describe the fields and the page it belongs on, and Insight builds it. Submissions are saved in your database, where you can browse them, and you can get an email each time someone sends one.
Transactional email
Email & pushEmail just works. Your app already sends sign-up codes, password resets and payment receipts, and any email your features need, like an order confirmation or a weekly summary, is added for you. There is no mail server to set up, and if your app speaks more than one language, each customer gets their emails in theirs. The Emails page shows what was sent and lets you put your brand on customer emails. If an address bounces, your app stops emailing it, marks that person on the Users page, and lets you send to them again once they fix it.
User roles & custom claims
AuthenticationSort the people in your app into roles, such as customer, staff or admin, so each one sees and does only what fits. Pick the role new people get, decide which roles people can choose themselves, and store extra details like a company name on every account. Having more than one role depends on your plan.
Related recipes
Morning prep list
Every morning, today's pre-orders and bookings arrive grouped by item and by time, ready to print for the kitchen or the front desk.
Tomorrow's bookings, the evening before
Every evening, you and your staff get tomorrow's bookings and pre-orders in one email, in time order, so prep starts on time and nobody is surprised.
Booking reminder email
The day before each booking, the customer gets a friendly email with the time, the place and a button to change or cancel, so fewer people forget to show up.