1. Onboard
We review fit, gather your operating details, and align on pickup windows, disclosures, and release logic.
The lowest-friction revenue channel you've never had.
12% commission. Zero delivery riders. Your restaurant name always front and centre. The only platform built to protect what you've spent years building.
Here's exactly how it works for your kitchen
You control the bag
Set your pickup window, allergens, cuisine type, and bag value. goZaika surfaces it to nearby consumers. You curate. We distribute.
No delivery operations
Your customer walks in, shows a QR code, picks up the bag. No rider coordination, no packaging SLAs, no delivery radius.
Your brand stays intact
Your restaurant name, cuisine identity, and story are front-and-centre on every listing. goZaika never describes your food as 'surplus' or 'leftover' to consumers. Ever.
Operationally, this is how it runs
2. Publish
Your team sets the bag value, allergens, cuisine type, quantity, and timing. goZaika turns that into a live listing.
3. Fulfil
Orders appear against your live release. Your team verifies QR pickup at handoff. No riders. No delivery coordination.
4. Reconcile
You receive settlement reporting, release performance, and operational visibility on what moved, when, and for whom.
Simple, transparent pricing
| Phase | Commission | Notes |
|---|---|---|
| First 30 days | 0% | Free onboarding period to launch your first bags without platform fees. |
| Pilot phase | 12% | Lowest-in-category commission while Hyderabad supply is being built. |
| Standard | 15% | Applies after pilot once the city network and demand loops mature. |
| Volume tier | 12% | Available for partners releasing 200+ bags per month. |
| Zayka Pro SaaS | INR2,499/mo | Optional software layer for deeper merchandising and reporting. |
How goZaika protects your brand
You control the bag. We never specify contents — that's your chef's decision.
No public discounting. goZaika is access-controlled, not listed on Zomato or Google.
Direct payouts. T+1 settlement via Razorpay. No intermediary hold.
Your name, front and centre. Every bag shows your restaurant brand to the customer.
Operational clarity for serious operators
Settlement timing
Settlements should be treated as a scheduled operating flow, not an ad-hoc reconciliation exercise. The page should communicate clear settlement windows tied to completed pickups.
Partner requirements
Partners should be FSSAI compliant, operationally reliable during pickup windows, and able to maintain accurate disclosure standards.
Sample dashboard / portal
Restaurants need a view of live releases, claimed bags, pickup status, customer-facing disclosures, and settlement visibility.
Customer support ownership
goZaika owns platform-side support and payment-path issues. The restaurant owns product quality at pickup and in-kitchen execution.
POS integration status
POS integration is not required for launch. The current model is operationally light and QR-led, with integrations introduced only where they remove real friction.
No-shows and volume tier
No-show handling should be explicit, and the volume tier should be explained as a meaningful threshold for recurring monthly release volume rather than a vague promise.
Why goZaika is different
Protect brand dignity
You decide what goes out, how it is framed, and who discovers it.
Commission that stays lean
The economics are designed to recover cost without creating delivery drag.
Pickup keeps operations simple
No riders, no dispatch complexity, and no compromise on kitchen control.
Ready to become a goZaika partner?
Share your details and our team will connect with you within 48 hours.
Operational FAQ
What does onboarding look like?
Onboarding covers operating fit, disclosures, pickup workflow, release logic, and launch readiness. We do not rush restaurants into a live state before those pieces are clear.
Who handles customer support?
goZaika handles platform and payment-path communication. The restaurant handles the in-store pickup experience and any kitchen-specific handoff issues.
Is POS integration required?
No. The initial operating model is intentionally light. QR verification and release management are enough for launch. Integrations come later if they remove real friction.
What happens on a no-show?
BAM Bags are tied to a declared pickup window. If a customer does not arrive, the bag is not held indefinitely. The operator should have a clear closure rule and the platform should communicate that policy upfront.
What does the volume tier mean in practice?
The volume tier is meant for partners releasing bags consistently enough to justify more favorable economics. It should be framed as recurring monthly release depth, not just sporadic spikes.