Design a recurring subscription order system
PremiumBackend systemMedium
- Recurrence rules
- Order cut off
- Idempotency keys
Quick answer
This backend system interview question asks you to design a recurring subscription order system. Aim for a design that meets its requirements at the stated scale, then explain its main components, data flow and trade-offs. Interviewers want to see how you scope the problem, size it and defend each choice.
The problem
Design a recurring subscription order system that lets users subscribe to items on a schedule, such as 2 milk packets every Monday, and places each order automatically, like the daily milk subscriptions in grocery delivery apps. The hard part is placing every due order exactly once, on time, while users keep editing.
Delivery is in the morning. Users can change, skip or pause tomorrow's items until a cut-off at 10 PM local time the night before.
What must a recurring subscription order system do?
- Schedules: Daily, alternate days, every N days or chosen weekdays, with a quantity per weekday and a start and optional end date.
- Auto orders: After the cut-off, the system places one order per user for the next delivery date with every due item.
How well must it do it?
- Exactly-once orders: Each user and delivery date gets at most one order and one debit, even if order generation crashes and reruns.
- On time: All orders for a night are placed within 60 minutes of the cut-off so packing can start.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Recurrence rules
- Order cut off
- Idempotency keys
- Batch order generation
- Prepaid wallet
- Inventory reservation
How you’ll practise
- Requirements
- Estimate
- API and data
- High-level design
- Deep dives
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any backend system design round.
- Clarifies the requirements before drawing anything
- Uses a few numbers that actually change the design
- Draws a clear path from the client to storage
- Picks storage and caching with reasons, not by habit
- Explains what breaks first under load and how to fix it
- States trade-offs openly instead of claiming a perfect design
Questions people ask about this interview question
- Which design type is this question?
- It is a backend system question. You design a recurring subscription order system and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
- What should I cover first?
- Start with the requirements: what the system must do, how well it must do it and which numbers change the design. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team