Delivery-aggregator readiness, not a connector or platform approval
Swiggy and Zomato POS integration readiness for Sholinganallur, Chennai
No native Swiggy or Zomato connector is verified in Posnic v1.3.0. Use one controlled manual or platform-approved test path to prove menu identity, order states, kitchen handoff, failures and reconciliation before rollout.
What the pinned Posnic evidence establishes
At exact source commit b531ef4308c4dc3a25f250551a54fc5616e3b8d9, a structured scan found four Zomato matches only in presentation-icon assets and no Swiggy or non-presentation brand match. None of 430 published OpenAPI paths names a brand, aggregator, webhook or callback. Seventeen selected route and sales call-path tests passed, but none is an aggregator integration test.
No native connector is verified
A scan of 2,979 tracked readable files found no Swiggy or Zomato product-logic implementation. Four Zomato matches were presentation-icon assets only.
A generic API is not platform approval
The published Posnic API exposes a protected sale path, but no branded connector, webhook contract, external-order identity or idempotency field was found.
Manual entry needs its own controls
If staff transfer an app order manually, preserve platform order identity, item mapping, charges, instructions, KOT evidence and a second-person exception check.
Approved integration is a full lifecycle
Zomato's official materials cover vendor onboarding, credentials, webhooks, menu, order and outlet states, testing, support and first live mapping. Each platform requires its own current approval evidence.
Unverified integration inputs for Sholinganallur
The location, currency, tax and payment values below are planning context. They do not establish platform eligibility, a Posnic connector, local restaurant mapping, provider approval, customer deployment, integration support or commercial outcome.
| Control | Current planning input | Evidence required before rollout |
|---|---|---|
| Search evidence | Four direct rows, 25 impressions and zero clicks | Query x Page x Country x Device evidence with date range, CTR, position and conversion before assigning a location winner. |
| Restaurant and platform | Sholinganallur, India; no accepted mapping | Named restaurant, outlets, platform, environment, transfer method, accountable owner and stop rule. |
| Product boundary | Posnic v1.3.0 at the pinned commit; no verified native connector | Exact connector source, release, architecture, dependency inventory and platform-review evidence. |
| Authorization | No vendor approval or agreement accepted | Current eligibility, agreement, platform contact, vendor and outlet IDs, sandbox access and live-mapping approval. |
| Credentials and webhooks | No branded endpoint or credential contract found | Endpoint ownership, authentication, secret storage and rotation, whitelisting, signatures, replay controls and platform configuration. |
| Menu identity | No accepted platform mapping | Stable category, item, variant, add-on, dietary, schedule and availability identities with one source of truth and rollback. |
| Price, tax and charges | Indian rupees; GST | Known carts prove item price, discounts, packaging, delivery, tax and final totals under current business-owner review. |
| Order identity | No reviewed external-order or idempotency field | One external order maps to one internal record across duplicate delivery, timeout, uncertain response and replay. |
| Order lifecycle | No platform state machine verified | Receive, validate, accept, reject, prepare, ready, pickup, delivery, timeout and cancellation states with actors and reasons. |
| Kitchen handoff | Bounded KOT components only | Every mapped line and instruction reaches the intended destination once; changes and cancellations remain linked and acknowledged. |
| Payment and settlement | Candidates: cash, UPI and cards | Separate platform and POS payment responsibilities; reconcile order counts, discounts, charges, refunds, settlement and exceptions. |
| Privacy and access | No platform data review accepted | Minimize permitted customer and delivery contact data; retain access, logging, retention and current applicable review. |
| Failure and fallback | No integrated outage or recovery result | Fail webhook delivery, platform API, local service, kitchen output and network separately with visible state and duplicate-free recovery. |
| Load, support and go-live | No accepted load result, escalation route or live mapping | Platform-required load and architecture evidence, monitoring, alert and escalation records plus supervised first-live approval. |
Run the 24-control aggregator acceptance path
Use synthetic restaurant and customer data first. Keep the result unverified until the exact platform approves the integration path, all failure and reconciliation cases pass, and one supervised live restaurant mapping is accepted.
- Name one restaurant, platform, service mode, current transfer method, accountable owner and stop rule.
- Record the exact Posnic build, platform agreement, vendor or restaurant identifiers, credentials owner, webhook endpoints and network dependencies.
- Map menu items, variants, add-ons, dietary tags, prices, taxes, charges and availability with stable identities.
- Trace one synthetic platform order through receipt, validation, acceptance or rejection, KOT, preparation, ready, pickup, cancellation and close states.
- Fail duplicate delivery, timeout, malformed payload, unavailable item, status callback and local dependency paths separately.
- Prove one durable external-to-internal identity and an approved retry decision before replaying any uncertain request.
- Reconcile platform orders, Posnic records, kitchen evidence, cancellations, discounts, charges and settlement for a fixed sample.
- Complete platform review, load and recovery evidence, support escalation and one supervised live mapping before claiming integration.
Questions about delivery-app POS for Sholinganallur
Does Posnic v1.3.0 include a native Swiggy or Zomato connector?
No verified native connector was found at the pinned source commit. A generic authenticated sale endpoint is not a platform integration or approval.
Is Posnic approved for Swiggy or Zomato integration in Sholinganallur?
No vendor approval, platform agreement, live restaurant mapping, local deployment or customer outcome is recorded on this page.
Can a restaurant transfer delivery-app orders manually?
A restaurant may evaluate a controlled manual process, but it must verify every item, price, charge, instruction, order identity, kitchen handoff and reconciliation. This is not an automated connector.
Can the generic Posnic API be used as proof of integration readiness?
No. The reviewed OpenAPI description documents a protected sale endpoint with a narrow public schema. It does not supply the platform webhook, menu, order-state, retry, support or approval contract.
What does Zomato require for POS integration?
Its current official documentation describes vendor onboarding, configured webhooks and authentication, API keys, critical feature parity, testing, legal agreement, support and first live restaurant mapping. Confirm the current requirements directly with Zomato.
Does this page prove Swiggy integration requirements?
No. The selected official Swiggy sources establish its marketplace and restaurant-partner context, not a Posnic connector or a technical approval path. Obtain current requirements directly from Swiggy.
What proves an aggregator rollout is ready?
Complete all 24 controls on the exact platform and restaurant configuration, resolve critical gaps, reconcile failures and settlement, and retain written platform and business approval.
Pinned Posnic product sources
These links expose the exact release, source, API description, routes, model and tests behind the boundary. They establish no native connector or platform approval.
Official platform, retry, security and recovery sources
Zomato's official integration pages describe its current vendor process. The selected Swiggy pages establish marketplace and restaurant-partner context only. The standards frame review controls; none certifies Posnic or establishes platform affiliation.
Related restaurant workflow pages
These links are navigation only. They do not prove a local restaurant, native connector, provider approval, platform mapping, customer result, integration support or onsite service.
Decision boundary for Sholinganallur
Posnic v1.3.0 has bounded generic sale, restaurant and KOT components, but this page does not establish a native Swiggy or Zomato connector, vendor approval, platform agreement, menu synchronization, external-order identity, duplicate-safe retry, complete state lifecycle, settlement, production recovery, live restaurant mapping, local customer or integration support commitment. Keep the result unverified until all 24 controls pass and the relevant platform and business owners approve the exact release.
Swiggy and Zomato names identify platforms being evaluated. Their trademarks belong to their respective owners. Posnic does not claim affiliation, endorsement or certification.
Integration owner evidence/Country-readiness method/Support routes