Petpooja

order-capture-floor-plan-editor

Dine-in areas with per-area menus/tax and 'customisable seating arrangements'; captains assignable to tables. No graphical shape editor or saved multi-layouts documented. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-01

order-capture-seat-level

Checked three surfaces. (1) blog.petpooja.com/operations-workflows/split-restaurant-bill-merge-tables-without-errors/ is a dedicated guide to splitting in POSS and tabulates exactly three divide methods - by percentage (equal shares), by price (each guest pays for the items they ordered), by proportion (share of dishes eaten together); none is seat-indexed. (2) www.petpooja.com/poss/bar-and-brewery-pos-software repeats the same three ('Split bills either by percentage, price or proportions'). (3) The Online Ordering API v2.1.0 OrderItem schema (jsapi.apiary.io/apis/onlineorderingapisv210.apib) carries id, name, price, quantity, description, variation and AddonItem - no seat or cover field; the Order block has only table_no and no_of_persons. Split-by-price gets an item onto the right guest's bill without re-keying, but nothing documents tagging a line to a seat number at entry. All three are feature descriptions or an aggregator-facing projection, not a configuration surface that enumerates the full split/seat model, so this is unresolved rather than absent.

order-capture-coursing-hold-fire

"A captain takes the full order upfront and holds the items in a wishlist, then fires the kitchen tickets course by course, from soups to starters to mains" - the worked sequence is take the order, hold in wishlist, "Fire the soup and starter tickets, and keep the mains on hold", then "Fire the mains once the starters are cleared". Hold-and-fire from the handheld is therefore present. Shortfall: the mechanism is a held wishlist that the captain releases by selection - no documented per-item course attribute, no named course sequence, and no fire-next-course action that knows which course is next; and this is described on a vendor guide page, not in configuration documentation. https://blog.petpooja.com/industry-business-guides/fine-dine-pos-what-handle-on-busy-floor/ · retrieved 2026-08-06

order-capture-split-merge

'Accept payments either by splitting bill or merging tables.' No documentation of by-seat, even N-way, arbitrary-amount, or post-partial-payment merge. https://www.petpooja.com/poss · retrieved 2026-08-01

order-capture-bar-tab-preauth differentiator

Checked www.petpooja.com/poss/bar-and-brewery-pos-software, which is the page that would sell this: it covers multi-terminal billing, station-wise KOTs, alcohol inventory, bill modifications ('going dutch or have a common tab' - split by percentage/price/proportion) and waiter/happy-hour reports, with no card pre-authorisation, no auth amount, no incremental re-auth and no stale-tab auto-close. blog.petpooja.com/industry-business-guides/bar-brewery-pos-india-liquor-pilferage-control/ is likewise about liquor stock and pilferage. The Online Ordering API v2.1.0 payment_type enum (jsapi.apiary.io/apis/onlineorderingapisv210.apib) is COD / CARD / CREDIT / ONLINE / OTHER with no auth-then-capture state, but that API is order relay from aggregators and is not the in-store tender surface. A running open tab clearly exists; a card pre-auth against it is neither shown nor denied on any Petpooja-owned page I retrieved.

order-capture-transfer-audit

"In Petpooja POSS you can merge or move tables on the fly, and the running order travels with the guests", and "The POS also records every table move. When items or a whole kitchen order ticket shift to another table, that change feeds the leakage panel, so an owner can see which table moved and when." The fine-dine guide repeats "table merge, move and split". Shortfall: only table-to-table movement is documented, and the recorded audit names the table and the time - there is no documented transfer of an open check between servers or between devices, and no audit entry naming both the releasing and receiving employee. https://blog.petpooja.com/operations-workflows/split-restaurant-bill-merge-tables-without-errors/ · retrieved 2026-08-06

order-capture-native-handheld

"Captain ordering app" appears in the Add-ons list on the vendor pricing page, not in any tier's included set. Native and first-party, yes; included, no. Price undisclosed. https://petpooja.com/poss/pricing · retrieved 2026-08-01 adversarially verified

order-capture-offline-order-entry

'Works perfectly well, even in offline mode'; Captain app 'supports offline architecture'. No published matrix of what does and does not work offline. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-01

order-capture-qr-same-check differentiator

The same-check behaviour is claimed verbatim ("every new order from the same QR links back to the same table bill"), but the page itself categorises Scan & Order as an add-on under "Customer service", and the pricing page lists "QR Ordering/Digital menu" as an add-on. Marketing claim + paid module = partial, not yes. https://petpooja.com/poss/scan-and-order · retrieved 2026-08-01 adversarially verified

order-capture-kiosk-first-party differentiator

Partial score stands, but the note misstates the ownership model: the kiosk hardware is Addsoft/Posbank; only the software is Petpooja's. Sizes 22"/27"/32", wall and floor mount, built-in thermal printer, WiFi+Bluetooth, UPI QR/cards. No ADA or accessibility language anywhere on the page — that part of the note is correct. https://petpooja.com/poss/self-service-kiosk · retrieved 2026-08-01 adversarially verified

order-capture-drive-thru

Enumerated www.petpooja.com/sitemap.xml (46 URLs, the whole published site - there is no help.petpooja.com or docs.petpooja.com; those hosts 404/500). The ten outlet-type pages under /poss/ are fine dine, QSR, cafe, food court, cloud kitchen, ice cream and dessert, bakery, bar and brewery, pizzeria and large chain; none is drive-thru, and neither /poss/quick-service-restaurant-software nor /poss/online-order-token-management mentions an order point, pay window, pickup window, lane assignment or pull-forward. The Online Ordering API v2.1.0 ordertypes master (jsapi.apiary.io/apis/onlineorderingapisv210.apib) is a closed set of three - Delivery, PickUp, DineIn (order_type H/P/D) - but that is the aggregator relay channel, not the in-store order-mode list. A site structure and a marketing page set are not an exhaustive capability enumeration, so absence is not established.

order-capture-drive-thru-timers

Checked www.petpooja.com/poss/reports-and-analytics and /poss/restaurant-analytics-insights, plus /poss/kitchen-display-system, for any per-order elapsed-time or segment timing; the KDS page describes displaying KOTs and marking food ready but publishes no timer or speed-of-service metric. The Online Ordering API v2.1.0 (jsapi.apiary.io/apis/onlineorderingapisv210.apib) carries minimum_prep_time, minimumpreparationtime and min_prep_time as forward-looking quote values plus an order status callback (accepted / dispatch / food ready / delivered), which is timestampable state but not a published drive-thru timer by segment. Since the drive-thru format itself is undocumented for Petpooja, timers for it are unresolved rather than absent - no Petpooja page states what the reporting suite does not contain.

order-capture-voice-ai differentiator

Petpooja publishes PetpoojaOnlineOrdering APIs v2.1.0, a credentialed partner API (app_key 32 chars, app_secret and access_token 40 chars) whose /saveorder endpoint injects a third-party order directly as a POS order with customer, items, variations, addons, taxes, discounts, charges, payment_type and prep time, plus fetch/push menu and an order-status callback. Any third-party voice agent would ride this path and the program is documented and open to integrators. Shortfalls: it is a general online-ordering partner program, not a voice-AI partner program - nothing in the spec or on petpooja.com addresses voice, telephony or drive-thru audio; and the only first-party voice feature is the Captain app's 'AI voice recognition' that helps a captain add items for billing (www.petpooja.com/poss/captain-ordering-app FAQ), a staff input aid, not a guest-facing ordering agent. The human-readable copy of this spec at onlineorderingapisv210.docs.apiary.io returned HTTP 502 on 2026-08-06; the blueprint source above served in full. https://jsapi.apiary.io/apis/onlineorderingapisv210.apib · retrieved 2026-08-06

order-capture-throttling differentiator

Read blog.petpooja.com/industry-business-guides/item-availability-menu-on-off-stop-cancelled-orders/, which is the closest thing Petpooja publishes to load control: manual item on/off, bulk category on/off ('When the kitchen falls behind on a Friday rush, you may want to pause every slow-cooked item at once'), and stock-threshold auto-pause that propagates to Swiggy and Zomato. That is availability suppression, not capacity: no orders-per-time-slot limit, no per-channel cap and no automatic quote-time extension. Also checked www.petpooja.com/poss/online-order-management-software and the Online Ordering API v2.1.0, where prep time appears only as fixed per-restaurant/per-item/per-order values (minimum_prep_time, minimumpreparationtime, min_prep_time) and the store-status endpoints toggle a store open or closed outright - a binary, not a throttle. None of these enumerates the configurable online-order settings, so a per-slot cap elsewhere in the admin is not excluded.

order-capture-scheduled-orders

Online Ordering API v2.1.0 /saveorder: preorder_date (yyyy-mm-dd) and preorder_time (HH:mm:ss) are both required, documented as 'For advance order the pre order date and time must be greater than or equal to current date and time of the system', with a validation error SO_105 when the preorder datetime is in the past; a separate advanced_order flag ('Flag which says that placed order is advance or not. Value is Boolean either Y or N') marks the order as advance, alongside urgent_order/urgent_time and an order-level min_prep_time 'defined by the order platform'. Future-dated acceptance is therefore documented. Shortfalls: lead time arrives per order from the platform rather than being configured per channel in Petpooja, and nothing in the spec or on www.petpooja.com/poss/kitchen-display-system documents holding an advance order out of the make queue until a computed fire time - the KDS is described only as displaying online and dine-in orders as they arrive. https://jsapi.apiary.io/apis/onlineorderingapisv210.apib · retrieved 2026-08-06

order-capture-catering

Enumerated www.petpooja.com/sitemap.xml: there is no catering or banquet page among the ten outlet-type pages, and the two catering items on blog.petpooja.com (/operations-workflows/food-catering-tips/ and /industry-business-guides/how-to-start-a-catering-business/) are general business advice with no Petpooja product flow in them. In the Online Ordering API v2.1.0 the order model carries preorder_date/preorder_time and an advanced_order flag, which covers a future-dated order, but the payment and total model has no deposit, part-payment or balance-due field (payment_type is COD/CARD/CREDIT/ONLINE/OTHER, plus a collect_cash amount for self-delivery COD), and there is no quote or event-schedule object. That is an aggregator relay schema, though, not the in-store order model, and no Petpooja page states that catering orders are unsupported - so this is unresolved, not absent.

order-capture-order-ready-signal differentiator

Online Ordering API v2.1.0, Order Callback: 'Online order integration partner must implement this endpoint to allow PoS patner to notify about order status updates post successfull order relay', with callback_url passed on every /saveorder call. The status enum is documented as '-1 = Cancelled, 1/2/3 = Accepted, 4 = Dispatch, 5 = Food Ready, 10 = Delivered', and the callback also returns minimum_prep_time 'conveyed by the restaurant', rider details on dispatch, and an is_modified flag. Food-ready is therefore pushed from Petpooja to the marketplace rather than tapped on the marketplace's own tablet; the source state is set in the POS or on the KDS, which www.petpooja.com/poss/kitchen-display-system documents as 'Mark food ready right from the KDS'. https://jsapi.apiary.io/apis/onlineorderingapisv210.apib · retrieved 2026-08-06

order-capture-void-comp-controls

User-rights management plus reports on 'bill modifications, discounted/cancelled orders'. Reason codes and manager-approval gating not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

menu-pricing-nested-modifiers

The addon field lists cited for this claim (item.addon = addon_group_id/addon_item_selection_min/addon_item_selection_max; addongroups = addongroupid/addongroup_name/addongroup_rank/active; addongroupitems = addonitemid/addonitem_name/addonitem_price/active/attributes/addonitem_rank) are accurate - I re-retrieved the full 116KB blueprint and confirmed them. They do not settle the claim, because the Online Ordering API v2.1.0 is by its own description the interface for orders received or placed from an online order aggregator, not the POS configuration surface. It claims no completeness and demonstrably omits per-item POS menu attributes - Petpooja documents item-wise multi-stage recipe management on /poss/restaurant-inventory-management-software and no recipe or raw-material field appears anywhere in the blueprint. Swiggy and Zomato cannot consume a third modifier level, so flattening on export is the expected design and absence from the export is not absence from the POS. No first-party page documents modifier nesting depth, per-level min/max or a forced-selection flag either way. I re-retrieved the blueprint (116KB, HTTP 200 under both a Googlebot and a plain UA, via jsapi.apiary.io and the /api-description-document route) and the field lists in the note are accurate. But an aggregator export is not an exhaustive enumeration of first-party menu configuration, and the corroborating pizzeria blog post is an editorial industry guide that asserts no completeness. I found no positive evidence the capability exists either, so this is unresolved, not absent.

menu-pricing-modifier-price-by-parent-size

'Item-wise variations, and add-ons with separate pricing for each customisation' implies per-item add-on pricing; a size x modifier price matrix is not documented. https://petpooja.com/poss/restaurant-menu-management-software · retrieved 2026-08-01

menu-pricing-fractional-placement differentiator

No section, half, placement or fraction field appears in the menu or order schemas - I verified that against the full blueprint. The inference fails because the Online Ordering API v2.1.0 is the aggregator relay channel by its own opening description, not the in-store menu configuration surface, and half-and-half placement is precisely the kind of POS-only construct an aggregator export would drop, since Swiggy and Zomato cannot consume it. The blueprint asserts no completeness and omits per-item recipe and raw-material data that Petpooja's own inventory page documents, proving it is lossy. The corroborating source, the July 2026 pizzeria guide on blog.petpooja.com, is an editorial industry guide rather than a configuration spec; it makes no completeness claim and its "100+ topping permutations" line is marketing. Searches of Petpooja's blog via its WordPress /wp-json/wp/v2/search endpoint and of the open web surfaced no Petpooja material affirming or denying half or quarter topping placement.

menu-pricing-half-and-half-rule differentiator

This cell was derived from menu-pricing-fractional-placement plus the pizzeria blog guide, and both legs fail the enumeration bar. The Online Ordering API v2.1.0 does carry one price per item, per variation and per addon, as noted - but it is the aggregator relay channel by its own description, asserts no completeness, and omits per-item POS attributes such as recipe linkage that Petpooja documents elsewhere, so it cannot establish which pricing rules the POS offers an operator. The pizzeria guide is editorial industry content with no completeness language. Because there is no evidenced finding that fractional placement is absent, there is no basis for concluding that a half-and-half pricing rule cannot be selected. I found no Petpooja source stating either way.

menu-pricing-topping-quantity-tiers

The note's reading of the spec is accurate - addongroupitems carry a single flat addonitem_price, the item-to-group link is documented as carrying the group id plus min and max selection and explicitly "Doesn't represents the quantity of addon items", and only the order line's AddonItem has a quantity. That establishes the shape of the aggregator export, not the shape of Petpooja's modifier configuration. The Online Ordering API v2.1.0 describes itself as the interface for orders received from online order aggregators, asserts no completeness, and omits per-item recipe data Petpooja sells as a POS feature, so it is a lossy projection. A light/regular/extra tier with a price multiplier is a POS-side construct aggregator menus do not model. No Petpooja page documents modifier quantity tiers either way.

menu-pricing-size-style-matrix differentiator

The variation array's fields (id, variationid, name, groupname, price, markup_price, active, item_packingcharges, variationrank, addon, variationallowaddon) are as described, and the order line carries a single variation_id - I confirmed both in the retrieved blueprint. That shows the export represents a flat list of priced variations. It does not show that Petpooja's menu builder cannot define a price across two variant axes, because the Online Ordering API v2.1.0 is the aggregator relay surface by its own opening description, claims no completeness, and drops per-item POS attributes - there is no recipe or raw-material field, though Petpooja sells item-wise recipe management. A size x crust grid would flatten to exactly this per-combination variation list on export, so the export is consistent with the capability existing. Petpooja's pizzeria guide describes size and crust as variations but is editorial content asserting no completeness.

menu-pricing-included-allowance differentiator

The addon link (addon_group_id, addon_item_selection_min, addon_item_selection_max) and the addon option master (addonitemid, addonitem_name, addonitem_price, active, attributes, addonitem_rank) contain no included-quantity, overage or substitution field, as noted, and I verified that. The enumeration does not qualify: the Online Ordering API v2.1.0 is the online-aggregator integration channel by its own description, asserts no completeness anywhere, and provably omits per-item POS menu data - Petpooja documents item-wise multi-stage recipes and the blueprint has no recipe field. An included-toppings allowance is resolved to a net price before an aggregator ever sees the line, so its absence from the export is expected whether or not the POS supports it. No Petpooja source addresses included-modifier allowances.

menu-pricing-combos

'Various combos, group offers, variations and add-ons.' Component swap with price delta and automatic a-la-carte-to-combo detection are not documented. https://petpooja.com/poss/pizzeria-and-pizza-shop-pos-software · retrieved 2026-08-01

menu-pricing-upsell-prompts differentiator

AI-based recommendation engine in the Captain app to help servers upsell. No per-channel configuration and no attach-rate reporting documented. https://petpooja.com/poss/captain-ordering-app · retrieved 2026-08-01

menu-pricing-86-propagation

Item availability toggles from stock propagate to POS, own online ordering, QR and aggregator menus. No published propagation latency. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

menu-pricing-countdown-auto-86 differentiator

Stock-driven auto item unavailability plus low-stock alerts. Per-item countdown/par counts and scheduled auto-restore are not documented. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01

menu-pricing-dayparting

Withdrawing the export-completeness leg: the Apiary blueprint is an aggregator-facing projection, so a field's absence in it establishes nothing about the POS. What carries the cell is affirmative. Grade A: the Online Ordering API v2.1.0 documents categorytimings as 'Active Schedule days and time slot of category' on every category, and group_categories as 'Contains groups created at menu category level. This will help identify the categories that are clubbed as a different menus configured in the restaurant menu management' - so configured menus and categories carry a day/time schedule that is pushed to the delivery apps. The previously stated shortfall 'items have no schedule of their own' is withdrawn and is in fact contradicted by Petpooja's own menu guide: 'a bakery counter may open pastries only from 4:00 p.m. ... Time-based menus let you set these windows once. The item appears and disappears on schedule, on both your counter and the delivery apps' (blog.petpooja.com/industry-business-guides/pos-features-for-menu-management/, retrieved 2026-08-06) - vendor guide prose rather than documentation, so it supports the limb but is not enough to carry a yes. Remaining shortfalls, stated as undocumented rather than absent: no scheduled base price change is described in any first-party source (only discounts carry day/time windows - discountdays, discounttimefrom/discounttimeto, discountstarts/discountends), and no source states which timezone a schedule evaluates in. https://jsapi.apiary.io/apis/onlineorderingapisv210.apib · retrieved 2026-08-06

menu-pricing-channel-price-books

Separate menus and pricing per dine-in area and per aggregator platform. Percentage-markup rules over a base price are not documented. https://petpooja.com/poss/restaurant-menu-management-software · retrieved 2026-08-01

menu-pricing-dual-pricing differentiator

Checked the Online Ordering API v2.1.0 item master (jsapi.apiary.io/apis/onlineorderingapisv210.apib): an item carries price and markup_price, and markup_price is documented as 'the strike price that can be displayed on the customer interface' - a was/now display device, not a cash-versus-card pair; per-channel pricing exists instead (item_ordertype, and Petpooja's menu guide describes 'different prices for dine-in and delivery'). Also read www.petpooja.com/poss/restaurant-billing-software (bill format and tax/discount configuration), /poss/restaurant-menu-management-software, and blog.petpooja.com/industry-business-guides/petpooja-finance-money-layer-in-pos/ - none describes a cash-discount or dual-price mode, and the receipt discussion covers e-bills, logo and GST break-ups only. This is not decisive: dual pricing is a tender-time behaviour that an aggregator menu export would not carry by design, and no Petpooja settings surface was published, so it stays unresolved.

menu-pricing-versioning-effective-dates differentiator

Read blog.petpooja.com/industry-business-guides/restaurant-menu-management-software-guide/, .../centralised-menu-management-uae-restaurants/ and .../sync-menu-across-swiggy-zomato-and-pos/, plus www.petpooja.com/poss/restaurant-menu-management-software. All four describe the same model: one live master menu, edited once, pushed immediately to counter, apps and kitchen ('the software holds one version of your menu and shares it everywhere', 'you edit the master, the update flows outward'). The word version there means single source of truth, not an effective-dated revision. No staging, no effective date, no pre-publish preview and no rollback is mentioned, and the Push Menu API carries no version, effective-from or draft field - but that endpoint is a full-menu snapshot push, which would look identical whether or not the admin supports staged versions. Time-bounded changes do exist for discounts (discountstarts/discountends), which is adjacent but not menu versioning. Nothing enumerates the menu admin's publish actions, so unresolved.

menu-pricing-franchise-hierarchy differentiator

"You keep one master menu per brand, then let each outlet or channel inherit it, with room to override where local prices differ. That way a chain sets a dish once at the head office and it lands the same way across every branch that carries it", and "For a multi-outlet brand, a head-office menu push is the real time-saver ... One update at the centre reaches every branch". The UAE guide (blog.petpooja.com/industry-business-guides/centralised-menu-management-uae-restaurants/) repeats it: one master menu, every branch and the central kitchen 'under the same account, with the same menu and reports'. Shortfall: override is described only as latitude on local price - there is no documented governance layer stating which attributes (price, name, availability, modifiers, tax, image) an outlet may or may not change, no lock or approval on a field, and no per-attribute permission matrix. Petpooja documents staff rights on the POS generally, but not field-level menu governance. https://blog.petpooja.com/industry-business-guides/restaurant-menu-management-software-guide/ · retrieved 2026-08-06

menu-pricing-allergen-nutrition

Every item in the Fetch/Push Menu payload can carry a nutrition object, documented field by field: calories (kcal), protien, totalFat, saturatedFat, transFat, cholesterol, carbohydrate, totalSugar, addedSugar, fiber, sodium, minerals[], vitamins[], additiveMap (Polyols, Polydextrose, Caffeine, ArtificialSweetener, MSG), foodAmount, servingInfo, additionalInfo, and allergens[] with 'Name of allergen present in food and a one line description' (allergen, allergenDesc). Items also carry item_attributeid (veg/non-veg/egg), item_tags (vegan, chef-special, new) and item_info.spice_level. Because these ride the menu push and fetch, they publish to online ordering and third-party marketplace menus. Petpooja's menu guide adds the driver: FSSAI menu labelling obliges chains with a central licence or 10+ outlets to show calorie and allergen detail everywhere, and it advises storing 'calorie, allergen and tax detail on each item record'. Shortfall: the spec states the values are merchant-supplied ('Merchant needs to provide these information in g, kg, ml or l') and the whole object is optional; recipe linkage in Petpooja is documented for stock and food cost, not for deriving nutrition, so the claim's derive-from-recipe-components limb is unmet. https://jsapi.apiary.io/apis/onlineorderingapisv210.apib · retrieved 2026-08-06

menu-pricing-recipe-linkage differentiator

Item-wise recipes with multi-stage recipe management and automatic stock deduction on sale. Item-level theoretical food cost output is not documented. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01

menu-pricing-3p-menu-push

Direct certified push of menu and pricing to Swiggy/Zomato from the POS. Per-item sync status and rejection-error surfacing are not documented. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

menu-pricing-dynamic-pricing

blog.petpooja.com/glossary/dynamic-pricing/ is a generic concept explainer, not a Petpooja feature page, and no page under www.petpooja.com/poss/ offers rule-based pricing. What the Online Ordering API v2.1.0 discount master does carry is time and day bounding - discountdays (Sun..Sat or All), discounttimefrom/discounttimeto, discountstarts/discountends, discountminamount, discountmaxamount, discountmaxlimit, discountordertype - which lets a price fall inside a window and caps the amount, and item_ordertype plus dine-in-versus-delivery pricing gives a channel differential. That is scheduled and channel pricing, not demand-responsive pricing, and there is no floor/ceiling guardrail on a computed price because no price is computed. The discount master is exhaustive for discounts but says nothing about whether a separate pricing-rule engine exists elsewhere in the admin, so unresolved.

payments-processor-choice differentiator

Petpooja is not an acquirer; it integrates payment gateways and UPI rails, so no in-house processing lock. No documented list of supported gateways. https://petpooja.com/poss/restaurant-website · retrieved 2026-08-01

payments-published-rates differentiator

No card-processing rate card is published because Petpooja does not underwrite processing; merchants price with their own gateway/acquirer.

payments-dual-pricing differentiator

Checked (1) the Online Ordering API v2.1.0 item master, where an item has one price plus markup_price, documented as a display strike price, and no second tender-specific price; (2) the same spec's order-level charge model - service_charge with sc_type/sc_calculate_on/sc_applicable_on/tax_on_sc, packaging_charge with packaging_applicable_on and packaging_charge_type, delivery charge with its tax ids - which enumerates the order-level charges and contains no card or cash differential; (3) www.petpooja.com/poss/restaurant-billing-software on bill format ('create bill break-ups', e-bills, dynamic QR) with no cash/card total pair; and (4) blog.petpooja.com/industry-business-guides/petpooja-finance-money-layer-in-pos/ and .../finance-compliance/card-vs-upi-why-restaurant-payment-reports-never-match/, which treat tender as something recorded after the price is set ('each transaction is classified by the method actually used'). None of these is the in-store tender configuration screen, and a cash-discount mode would not appear in an aggregator menu export, so this remains unresolved rather than absent.

payments-surcharge-guardrails differentiator

Read blog.petpooja.com/industry-business-guides/petpooja-finance-money-layer-in-pos/, which describes the whole payments layer: Petpooja Pay+ routes a card/UPI/QR request through Finance Cloud to a chosen partner acquirer (live partners named as Paytm, Razorpay, Pine Labs, Mosambee, BharatPe), and Finance then reconciles the partner's payout and shows provider MDR per swipe. Petpooja therefore sits above the card rails and no BIN, product-code or card-type data is described as reaching it; nothing about a surcharge percentage, a debit/prepaid exclusion or a network cap appears there, on www.petpooja.com/poss/restaurant-billing-software (which covers taxes and discounts), or in the Online Ordering API charge model (service charge, packing, delivery only). Also read .../finance-compliance/card-vs-upi-why-restaurant-payment-reports-never-match/, which discusses MDR as a deduction from settlement rather than a customer surcharge. No published page enumerates the configurable charges at the till, so unresolved.

payments-emv-nfc

Verified verbatim: "Single tap contactless card payments under INR 5000". Note this is India's PIN-free contactless ceiling, so it is not general EMV acceptance — above that limit the flow is undocumented. No first-party terminal line, Apple Pay/Google Pay unnamed. Partial is correct. https://petpooja.com/poss/captain-ordering-app · retrieved 2026-08-01 adversarially verified

payments-softpos-tap-to-pay differentiator

Contactless card acceptance on a standard Android phone via the Captain app; not explicitly branded as Tap to Pay on Android SoftPOS. https://petpooja.com/poss/captain-ordering-app · retrieved 2026-08-01

payments-pay-at-table

Depends entirely on the add-on Captain app. Also, the vendor's own summary of settlement on that page is narrower than the dossier's note: "Your captain can take multiple orders and settle bill using cash and a QR code"; the card element is the separate line "Single tap contactless card payments under INR 5000", i.e. capped low-value contactless only. Not a general pay-at-table card flow. https://petpooja.com/poss/captain-ordering-app · retrieved 2026-08-01 adversarially verified

payments-qr-guest-pay differentiator

The billing page says only "add a dynamic QR code for payments right at the billing counter" - a counter-presented collection QR, not a QR on the check or table tent. The Scan & Order page offers "Pay at counter or pay online" but never states that the guest views the check or that an online payment settles and closes the bill in the POS. Shortfall: check-view-and-close behaviour undocumented, and "Scan and pay QR" is listed as a paid add-on rather than an included capability. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-02 adversarially verified

payments-tip-adjust

"Tips have a setting worth checking. In Petpooja POSS the suggested tip can be worked out on the Core amount, which is the subtotal before tax and charges, or on the Total bill value, which is the default" - so a configurable tip prompt exists on the bill, distinct from the statutory-voluntary service charge, and it survives a split. Shortfalls: nothing documents a pre-authorisation followed by a tip adjustment, no batch or adjust window is published, and there is no manager screen for unadjusted tips. Petpooja's day-end guide (blog.petpooja.com/finance-compliance/restaurant-day-end-report-how-close-and-reconcile/) instead treats an EDC tip as an unreconciled gap - "A tip added on the card machine but not on the bill leaves a small difference" - advising a tolerance rather than an adjust step, which indicates tips taken on the partner card terminal do not flow back into the check at all. https://blog.petpooja.com/operations-workflows/split-restaurant-bill-merge-tables-without-errors/ · retrieved 2026-08-06

payments-tip-pooling differentiator

Searched blog.petpooja.com (WordPress search API) for tip pooling, tip distribution and gratuity; the only tip content in the corpus is the POSS suggested-tip basis setting (core vs total) in .../split-restaurant-bill-merge-tables-without-errors/ and the day-end note that an EDC tip not on the bill leaves a reconciliation gap. Checked www.petpooja.com/payroll (Attendo, formerly Petpooja Payroll) and the people-and-payroll blog category for an earnings component or allocation rule covering tips - the material covers salary, attendance, ESIC/PF and self-service portals, with no tip pool, no allocation by hours/sales/role/points and no per-employee tip export. Petpooja does publish waiter performance reports (www.petpooja.com/poss/bar-and-brewery-pos-software), which attribute sales but not tips. None of these enumerates the payroll earnings components, so unresolved.

payments-offline-store-and-forward differentiator

The guide sets out what does and does not survive an outage: "The part you need during service keeps working: billing, KOT printing and table management. What stops is any task that travels over the internet, mainly Swiggy and Zomato orders plus card payments routed through an EDC." Its FAQ repeats it - "card or UPI on an EDC needs a connection of its own" - and its outage runbook tells staff to "Switch payments to cash or a direct UPI QR" or tether a phone hotspot to "restore card payments". Offline capability is limited to bills, KOTs and settlements held on the machine for up to 5 days on Electron POS, Android POS and POS Local (POS Lite has no offline mode) and syncing on reconnect. No card is captured offline, so there are no per-transaction or cumulative offline card limits to configure. This is a positive vendor statement of what stops, not a failed search. https://blog.petpooja.com/industry-business-guides/restaurant-pos-without-internet/ · retrieved 2026-08-06

payments-offline-decline-liability differentiator

The same offline guide that rules out offline card capture defines what reconnect does: "bills, KOTs and settlements are stored on the machine. When the line returns, it all syncs on its own. You do not re-enter anything, and your day-end totals include the offline bills", with offline tenders being cash or a direct UPI QR taken outside the EDC. There is therefore no stored card authorisation to be declined on reconnect, and no post-reconnect failed-payment report exists or is published; correspondingly Petpooja publishes no allocation of loss for such a decline, on this page, on www.petpooja.com/terms-and-conditions or on any Finance page. Recorded as no because the underlying scenario is documented not to occur, not because a statement could not be found. https://blog.petpooja.com/industry-business-guides/restaurant-pos-without-internet/ · retrieved 2026-08-06

payments-gift-cards

Loyalty Wallet stores value topped up by cash/card/UPI with virtual cards and OTP redemption. Not framed as gift cards; cross-outlet redemption not documented. https://petpooja.com/poss/restaurant-loyalty-program · retrieved 2026-08-01

payments-house-accounts

"Petpooja POSS supports this through customer-card top-up and a credit flow, run on its Virtual Wallet ... An office or college canteen can let staff and students order on credit against their account, then settle the balance at the end of a cycle", with the running balance live at the till ("Every order at any counter deducts from that balance, and the remaining amount is shown at billing") and "A canteen manager can pull a wallet or credit report instead of maintaining a side register." On-account tabs and a running balance are therefore documented. Shortfalls: no per-account credit limit or ceiling is described anywhere, and the reporting is a wallet/credit report rather than a periodic statement or invoice issued per account - no billing cycle, statement run or invoice generation is documented. https://blog.petpooja.com/industry-business-guides/food-court-canteen-pos-multi-counter-billing/ · retrieved 2026-08-06

payments-split-tender

Bill splitting is documented. Multi-tender settlement of one check, split-by-seat and an eight-way floor are not documented. https://www.petpooja.com/poss · retrieved 2026-08-01

payments-refund-void-controls

User-rights management plus reports on cancelled/modified bills and cash-drawer operations. No documented immutable audit log naming the approver. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

payments-chargeback-tooling differentiator

Read blog.petpooja.com/industry-business-guides/petpooja-finance-money-layer-in-pos/ in full, the only published account of the payments dashboard at finance.petpooja.com. Its capability breakdown covers payment processing through connected EDC and QR devices, tender classification on Pay+ (card under Card, UPI and Bharat QR under UPI), payout reconciliation that flags transactions missing invoices and shows provider charges next to the final payout, Soundbox confirmation, and banking (HDFC current account, loans). No dispute or chargeback list, no evidence submission and no representment workflow appears, and the acquiring relationship sits with the partner (Paytm, Razorpay, Pine Labs, Mosambee, BharatPe), which is where a dispute would normally be worked. That is a vendor guide rather than a screen inventory, and finance.petpooja.com is behind a merchant login I did not access, so absence is not established.

payments-card-on-file differentiator

Checked three surfaces. (1) The Online Ordering API v2.1.0 Customer object is enumerated as email, name, address, phone, latitude, longitude - no token, no saved instrument, and payment_type is a plain enum (COD/CARD/CREDIT/ONLINE/OTHER) with no reference to a stored credential; but the aggregator collects payment on that channel, so a POS-side vault would not appear here. (2) www.petpooja.com/poss/restaurant-customer-management-software describes the guest profile as contact data, visit history, feedback and loyalty points, with no payment instrument. (3) blog.petpooja.com/industry-business-guides/petpooja-finance-money-layer-in-pos/ describes Pay+ as routing each payment request through Finance Cloud to a partner acquirer per transaction, with no mention of tokenisation, saved cards or repeat billing (India's RBI card-on-file tokenisation regime would make this a documented feature if offered). Nothing published enumerates what the guest profile can store, so unresolved.

payments-payout-timing differentiator

blog.petpooja.com/finance-compliance/card-vs-upi-why-restaurant-payment-reports-never-match/ describes settlement in the third person throughout - "The provider settles the remaining amount to your account, usually on the next working day", "Card settlements usually arrive the next working day, sometimes later over a weekend", and advice to "Compare the acquirer's payout report to the right dates" - and .../petpooja-finance-money-layer-in-pos/ frames Petpooja Finance as checking "what the provider actually paid" against sales, with Pay+ routing to a chosen partner (Paytm, Razorpay, Pine Labs, Mosambee, BharatPe). That is a vendor description of the acquirer's schedule, not a Petpooja deposit schedule, and no instant or same-day funding product appears on any petpooja.com page or in the Finance material. I stopped short of no because third-party software listings advertise 'T+1 disbursal' and 'card payout in one hour' for Petpooja and I could not open a Petpooja-owned page stating or denying such an option - finance.petpooja.com is behind a merchant login.

payments-multi-entity-routing differentiator

Read blog.petpooja.com/industry-business-guides/run-multiple-outlets-one-pos-local-system/, .../food-court-canteen-pos-multi-counter-billing/ (unlimited terminals on one account, counter-wise and combined reporting) and www.petpooja.com/poss/large-chain-restaurant-pos-software: all describe one account spanning outlets with unified reporting, which is the claim's reporting half, but none says anything about where each outlet's money lands. The Petpooja Finance guide covers a single HDFC current account application per owner and per-provider payout reconciliation, without a per-outlet or per-entity bank mapping. In the Online Ordering API the restaurant is identified by restID/mappingid with no bank or MID field, and GST liability is split only between vendor and restaurant for aggregator settlements. Since settlement is executed by the partner acquirer rather than Petpooja, the routing question may not be Petpooja's to answer, but nothing published states either way.

payments-p2pe-pci4

trust.petpooja.com returns HTTP 200 but the body is a Next.js shell that loads the app/not-found chunk; its content lives under a /sites/<slug> route and every slug I tried (petpooja, poss, home, main) returned 404, and /sitemap.xml returns the same HTML shell rather than a sitemap - so no certification content was served to me. www.petpooja.com/security, linked as Security in the footer, is the Vulnerability Disclosure Program page (safe harbour, reporting guidelines, scope of *.petpooja.com production systems) and contains no attestation, no PCI DSS reference and no P2PE listing. Grepped the retrieved corpus - all 46 sitemap URLs' product pages plus 19 blog articles including the payments and POS-architecture ones - for PCI, P2PE, SOC 2 and ISO 27001: the only hits are NPCI in a UPI-volume citation. Petpooja also routes card acceptance through partner acquirers (Paytm, Razorpay, Pine Labs, Mosambee, BharatPe) whose own PCI posture is not Petpooja's attestation. Unresolved: the trust centre plainly exists and would be the place this is published, but it served no readable content.

kitchen-station-routing

Station-wise order allocation on KDS plus per-station printer assignment configurable from the POS. https://petpooja.com/poss/kitchen-display-system · retrieved 2026-08-01

kitchen-expo-consolidation

Can run as a central screen or multi-display per kitchen, synchronised across devices. Completion gating until every station bumps is not documented. https://petpooja.com/poss/kitchen-display-system · retrieved 2026-08-01

kitchen-course-firing differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. Read /poss/restaurant-billing-software, /poss/kitchen-display-system, /poss/captain-ordering-app and /poss/fine-dine-restaurant-pos-software: none mentions courses, seat/course assignment, holding or firing. The API blueprint's OrderItem object (id, name, variation, AddonItem, taxes, discounts) carries no course or hold field. With no admin guide published anywhere, presence cannot be confirmed or excluded.

kitchen-prep-time-pacing differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. In the Push/Fetch Menu schema, 'minimum_prep_time - Minimum preparation time of restaurant in minutes' sits on the restaurant details object only; the item object (nutrition, cuisine, item_tags, item_info, markup_price, variations, addons) carries no cook time. /poss/kitchen-display-system describes only individual KOTs, an aggregated item list and mark-food-ready, with nothing about staggered start or simultaneous finish. Not scored 'no' because that schema is an aggregator-facing export and need not mirror the internal item master.

kitchen-order-throttling differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. The only documented pacing lever is the API's Update Store Status endpoint with a 'turn_on_time' key (changelog 01-04-2023), i.e. an operator-driven store on/off with a reopen time, plus the restaurant-level minimum_prep_time. Nothing on /poss/online-order-management-software or /poss/cloud-kitchen-pos-software describes a volume or ticket-time threshold that automatically delays release or extends the quote.

kitchen-channel-pause-propagation differentiator

I re-fetched the cited page. It supports item-level control from one screen - "toggle any online menu item On or Off as per your inventory" and "Add store timing, packaging charges, and discounts. Easily manage the online menu for your single or chain outlets from one single screen" - but I could find no sentence on it, or on any other first-party page, about pausing a store/outlet on Swiggy or Zomato from the POS, nor any statement that these changes propagate automatically rather than being pushed by the operator. Shortfall: item availability only, manual, store-pause propagation unevidenced. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-02 adversarially verified

kitchen-order-ready-callback differentiator

Order Callback in the first-party Online Ordering API v2.1.0 defines the status enum '[-1 = Cancelled, 1/2/3 = Accepted, 4 = Dispatch, 5 = Food Ready, 10 = Delivered]', posted by Petpooja to the callback_url the integration partner supplies on every Save Order request, alongside minimum_prep_time and (on status 4, self-delivery) rider_name and rider_phone_number. The ready state originates at the kitchen screen: /poss/kitchen-display-system lists 'Mark food ready right from the KDS' and /poss/online-order-token-management 'Manage orders and mark food ready from your POS or KDS'. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

kitchen-bump-bar-hardware

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/kitchen-display-system's own hardware FAQ asks 'What type of hardware will I need to use KDS?' and answers only 'Petpooja's KDS works perfectly well with any Windows or Android-based device'; a second FAQ covers multi-device/station use. No supported-model list, peripheral page or hardware compatibility table exists anywhere in the sitemap. That answer is about the host device and does not exclude a USB HID bump bar, so this is unresolved rather than absent.

kitchen-all-day-counts

KDS shows individual KOTs alongside aggregated item lists. Modifier-level all-day aggregation is not documented. https://petpooja.com/poss/kitchen-display-system · retrieved 2026-08-01

kitchen-sla-alerts

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/kitchen-display-system enumerates its feature bullets as: online and dine-in orders on the kitchen screen, no paper KOT, Android/Windows, individual KOTs plus aggregated item list, mark food ready. No target cook time, colour escalation or overdue alert. /poss/online-order-token-management documents a voice notification but it fires when an order is marked food ready, not when a target is breached. The API exposes only a restaurant-level minimum_prep_time, not per-station targets.

kitchen-printer-fallback differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/restaurant-billing-software documents station printer assignment - 'Assign a unique printer to every station and send KOTs to the respective stations' - and /poss/kitchen-display-system multi-screen station allocation, but neither describes what happens when a screen or printer is offline. No backup-device or failover setting is published.

kitchen-offline-operation differentiator

Offline architecture is asserted for the platform including KDS, but the specific offline KDS behaviour is not spelled out. https://petpooja.com/poss/kitchen-display-system · retrieved 2026-08-01

kitchen-item-build-screens differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/kitchen-display-system says the KDS 'Displays individual KOTs and aggregated item list'; a customer testimonial on the same page refers to menu customisation requests being visible to kitchen staff, but that is marketing copy and does not establish a build/assembly view. Recipe definition appears only in /poss/restaurant-inventory-management-software as a costing construct ('recipe costs'), with no documented route to a station screen.

kitchen-pizza-fractional-display differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/pizzeria-and-pizza-shop-pos-software describes topping handling as 'you can sell by the slice, or give 100 different toppings' and combos/variations/add-ons, with no sectioned or fractional placement. The API's AddonItem object carries id, name, group_name, group_id, price and quantity, with no section/portion attribute. Since the pizzeria page is marketing and the addon schema is aggregator-facing, this is unresolved rather than a finding of absence.

kitchen-recall-refire

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. No recall, unbump or refire language on /poss/kitchen-display-system or /poss/restaurant-billing-software. The API's Update Order Status endpoint states 'As of now, this endpoint can be used to send only cancel order (-1) status', which speaks to the partner interface, not to in-store KDS recall. Unresolved.

kitchen-order-modification-alerts differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. Order modification after transmission is a modelled concept: the order callback carries 'is_modified - Order is modified at the restaurant or not', and Update Order Status returns error UOS_105 'when order is modified or status of order is changed by restaurant'. What is not documented anywhere is how an edit is rendered on a ticket already showing on the KDS - /poss/kitchen-display-system says nothing about added/changed/removed item highlighting.

kitchen-guest-ready-notification differentiator

Token Management, Digital Display System, SMS Service and a Wireless Calling Device exist - but as separately purchased marketplace add-ons, not bundled. https://petpooja.com/poss/restaurant-app-marketplace · retrieved 2026-08-01

kitchen-waste-logging

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/kitchen-display-system's FAQ 'Can my chef use KDS to manage kitchen inventory?' answers with exactly two actions - 'mark any inventory out of stock and mark food ready' - with no waste, spoilage, remake or reason-code entry. /poss/restaurant-inventory-management-software documents returning 'the damaged stock back to its source' in the central-kitchen flow, which is a transfer, not a KDS waste log. Left unknown because a marketing FAQ is not an exhaustive settings enumeration.

kitchen-speed-of-service-reporting

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/reports-and-analytics and its FAQ name sales, item-wise consumption, online orders, staff scheduling, bill modification, discount/cancellation and cash-drawer reports, plus emailed report alerts and outlet-wise report rights; /poss/restaurant-app-marketplace advertises '40+ insightful reports' and a Dynamic Reports add-on. No report catalogue is published, so ticket time, per-station time or percentile breakdowns can be neither confirmed nor excluded.

kitchen-prep-forecasting

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. Checked /poss/restaurant-inventory-management-software (purchase orders, central kitchen, recipe costs, low-stock alerts on the billing screen, e-way bills), /poss/purchase-manager and /poss/restaurant-analytics-insights. Procurement pre-planning is claimed on /poss/pizzeria-and-pizza-shop-pos-software ('Pre-plan inventory procurement') but no forecast-driven prep list or predicted prep quantity surfaced to kitchen staff is described.

delivery-driver-roster

Petpooja's own delivery documentation enumerates the alternative - integrated third-party rider apps (Duzno, Shadowfax, Pidge) - rather than a native in-house driver module. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

delivery-dispatch-board

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/online-order-management-software leads with 'Accept multiple orders, manage riders', but its own FAQ resolves that to third parties: 'Petpooja's restaurant billing software supports more than 150+ different third-party integrators, including ride management apps like Duzno, Shadowfax, and Pidge'. No screen showing undispatched orders, driver availability, elapsed time or multi-order run batching is documented on any /poss page, and the add-on catalogue at /poss/restaurant-app-marketplace lists no dispatch module.

delivery-route-map differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. No map, geocoded stop list or route sequencing is described on /poss/online-order-management-software, /poss/cloud-kitchen-pos-software or /poss/restaurant-app-marketplace. The API blueprint contains no route, sequence or distance field; customer latitude/longitude arrive on inbound orders only. The inter-outlet 'delivery route' language elsewhere in this record belongs to stock transfers, not customer delivery.

delivery-driver-tracking differentiator

Rider Information webhook: a third-party logistics provider POSTs order_id, outlet_id, status 'rider-assigned/rider-arrived/pickedup/delivered' and rider_data {rider_name, rider_phone_number} to Petpooja 'in order to update the order delivery status at our end without continuously polling with check order status'; the order callback likewise returns rider_name and rider_phone_number on status 4 (Dispatched) 'in case of self-delivery'. Shortfall: these are discrete milestones with no latitude/longitude and no live position; the webhook 'has to be provided by third party', no first-party Petpooja driver app is documented (/poss/online-order-management-software points rider management at Duzno, Shadowfax and Pidge), and no dispatch screen that plots a rider exists in any published page. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

delivery-zones-polygon differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. The Push/Fetch Menu restaurant details object enumerates the delivery configuration Petpooja exports as scalars - minimumorderamount, minimumdeliverytime, deliverycharge, deliveryhoursfrom1/to1/from2/to2 - with no zone, polygon, radius or geometry object anywhere in the blueprint. No /poss page describes drawing a delivery area. Left unknown rather than 'no' because that export describes the aggregator-facing view and need not carry first-party widget zone config.

delivery-zone-pricing

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. Same schema evidence as delivery-zones-polygon: one deliverycharge, one minimumorderamount and one minimumdeliverytime per restaurant in the menu API, never an array keyed by zone; on inbound orders delivery_charges/dc_tax_percentage are set by the ordering platform, not derived by Petpooja. /poss/online-order-management-software documents only packaging charges and store timing as operator-side fee controls. Not scored 'no' because the aggregator-facing schema is not an exhaustive enumeration of first-party ordering settings.

delivery-address-validation

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. In Save Order, the Customer details object receives address, latitude and longitude from the ordering platform - Petpooja is the recipient of an already-geocoded address and the blueprint documents no address validation or out-of-zone rejection on its side (the validation_errors object is described generically as 'various errors which can be arised while placing order'). /poss/restaurant-website covers the first-party ordering widget, hosting, domain and Razorpay only, saying nothing about address entry.

delivery-driver-comp differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. Read https://www.petpooja.com/payroll end to end: shifts (including overnight and multi-shift), leave types and approvals, fingerprint and location-based attendance, PF/ESIC/PT breakdown, overtime and late-entry penalties, loans and advances auto-deducted from salary, and '6+ industry-standard reports'. No mileage or distance capture, no per-delivery reimbursement line, no driver-retained tip handling, and no rider pay concept at all. Rider identity in the API is limited to name and phone, with no compensation fields.

delivery-cash-reconcile

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. Cash-on-delivery is modelled at the order level - Save Order carries payment_type 'COD' and 'collect_cash' (changelog 29-12-2023) - so the amount a rider must collect is known per order. What is not documented is any driver bank, settle-up or end-of-shift over/short flow: /poss/reports-and-analytics names cash-drawer operation reports at the till level only, and no /poss page describes reconciling a rider's collected cash against orders assigned.

delivery-daas-dispatch

Rider-management app integrations with on-demand logistics providers (Duzno, Shadowfax, Pidge) are supported. Quote-and-status return into the order record is not documented. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

delivery-daas-fallback differentiator

FAQ: 'Can I use rider management apps with my restaurant POS? Petpooja's restaurant billing software supports more than 150+ different third-party integrators, including ride management apps like Duzno, Shadowfax, and Pidge', and the API blueprint's Rider Information webhook gives those couriers a documented path to push rider-assigned/arrived/pickedup/delivered back into the order - so handing a delivery to a DaaS courier is supported. Shortfall: no rule engine is documented. Nothing on any /poss page or in the blueprint describes automatic overflow when no in-house rider is available, when an address is out of zone, or past a wait threshold; the handoff appears operator-initiated. https://www.petpooja.com/poss/online-order-management-software · retrieved 2026-08-06

delivery-3p-direct-integration differentiator

Partial stands, but the named set is over-stated. On the cited page I could only confirm "Swiggy, Zomato, Dineout" plus rider apps "Duzno, Shadowfax, and Pidge". District and EazyDiner are not evidenced on that URL — treat those two names as unverified. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01 adversarially verified

delivery-3p-injection

Aggregator orders land on a single acceptance screen inside the POS and flow to KOT/KDS with no tablet re-keying. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

delivery-menu-push

Menu and pricing updates publish from the POS master menu to all connected aggregators simultaneously; packaging charges configurable per channel. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

delivery-86-sync

'Toggle any online menu item On or Off as per your inventory' with automated stock-out management cross-checked against POS stock. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

delivery-store-pause

Store timing and pause management from inside the POS. Timed auto-reactivation is not explicitly documented. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

delivery-3p-reconciliation differentiator

I fetched the cited page myself. It is marketing copy (testimonials, problem/solution framing, CTAs), not product documentation — so "documented" confidence is unearned. More materially, its own FAQ says "Reach out to your Petpooja account manager for availability and pricing details for your plan", i.e. reconciliation is a paid add-on of unpublished price and unstated tier availability, not a bundled capability. The named behaviours (matched orders, status mismatches, amount variances, missing orders in both directions, per-order commission) are all present as claims, so the capability is rea https://petpooja.com/poss/online-order-reconciliation · retrieved 2026-08-01 adversarially verified

delivery-injection-error-visibility differentiator

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. The blueprint does define machine-readable failure surfaces - Save Order errors SO_105 and SO_106 with a validation_errors object, Update Order Status error UOS_105, and Get Store Status / Update Store Status endpoints for per-channel store on/off - but every one of these is consumed by the integration partner, not shown to the restaurant. No /poss page describes an operator-facing integration health view, a failed-injection list or failure alerts; the closest is the paid Online Order Reconciliation add-on, which matches aggregator payout sheets against POS records after the fact rather than alerting live.

delivery-tracking-page

Retrieval for this vendor: enumerated https://www.petpooja.com/sitemap.xml (46 URLs, all marketing/feature pages, no docs tree) and read every /poss/* page; support., help., kb., docs., developer., api. and online-order.petpooja.com all 404/500, petpooja.zendesk.com help_center API 403, developerapi.petpooja.com 403. The only primary technical doc is the first-party Online Ordering API v2.1.0 blueprint at onlineorderingapisv210.docs.apiary.io. /poss/online-order-token-management is an in-store Android TV display for takeaway customers and delivery executives waiting at the counter, not a guest-facing link. /poss/restaurant-website documents the ordering widget, hosting, domain purchase, plug-ins and Razorpay but no order-status or driver-tracking page; /poss/restaurant-sms-service is campaign marketing SMS with no transactional order-status template. No first-party branded tracking page is described, and none is excluded either. Review-site claims were deliberately not used.

delivery-promise-time differentiator

The quote is modelled at two levels rather than as one fixed store constant: the Push/Fetch Menu restaurant object carries 'minimum_prep_time - Minimum preparation time of restaurant in minutes' (added 12-09-2024) and 'minimumdeliverytime', while Save Order accepts an order-level 'min_prep_time - order level Kitchen preparation time defined by the order platform' and the order callback returns 'minimum_prep_time - Kitchen preparation time conveyed by the restaurant' plus 'minimum_delivery_time - Delivery time mentioned by restaurant'. Shortfall: every documented value is asserted by the restaurant or the ordering platform; nothing in the blueprint or on any /poss page describes automatic derivation from current kitchen load, rider availability or zone drive time, and there are no drive-time or zone fields at all. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

delivery-offline-behavior

This claim asks whether the vendor documents delivery offline behaviour, so a no requires the published corpus to be provably complete. The prior enumeration was www.petpooja.com/sitemap.xml (46 URLs) plus the /poss FAQ answers. That premise is false: I retrieved the sitemap myself, confirmed 46 URLs and no blog entries, and Petpooja's most detailed offline documentation - a dedicated article with a what-keeps-working versus what-waits-for-the-line pair and a per-POS-type offline table (POS Lite no; Android POS, POS Local and Electron POS yes, up to 5 days) - sits at blog.petpooja.com/industry-business-guides/restaurant-pos-without-internet/, entirely outside that sitemap. The blog is a separate WordPress property whose own post sitemap carries roughly 800 posts. Since the enumerated corpus demonstrably excludes the vendor's own offline documentation, silence within it cannot establish that delivery offline behaviour is undocumented. That dedicated article is itself silent on cash delivery orders, rider assignment and rider settlement during an outage - it addresses Swiggy and Zomato order intake and EDC payments - so the claim is unresolved rather than answered.

digital-first-party-web

"Restaurant website" is listed among Add-ons on the vendor pricing page, not included in any tier. The "without paying a single penny to third-party applications" line is comparative marketing about aggregator commissions, not a statement that the module is free. https://petpooja.com/poss/pricing · retrieved 2026-08-01 adversarially verified

digital-menu-single-source

'Upload and manage your website menu using POS' - the ordering site is driven from the POS menu record. https://petpooja.com/poss/restaurant-website · retrieved 2026-08-01

digital-native-app differentiator

Petpooja's guest-facing direct channel does appear to be a hosted website plus an ordering widget, and I found no branded consumer app - the Petpooja apps in the public stores are the Merchant app and the Captain app, both staff-facing. But the basis for asserting absence does not meet the bar. I re-fetched www.petpooja.com/poss/pricing: its only completeness-adjacent language is "A clear breakdown of what each plan offers", which promises a per-plan breakdown rather than an exhaustive product catalogue; it is a grade-C page written to sell, and its rows sit behind "Show More" controls. The second leg, the 11-service catalogue on /poss/restaurant-app-marketplace, is an app directory, which the enumeration bar excludes outright. A branded consumer app is also commonly delivered through partners rather than as a plan line item, and Petpooja's "150+ integrations" partner list renders as a single flat CDN image and cannot be enumerated at all. Unresolved rather than absent.

digital-account-saved-payment

Checked https://www.petpooja.com/poss/restaurant-website (the first-party ordering product and its six-question FAQ, which covers hosting, domains, plug-ins, SEO and the ordering widget only), /poss/restaurant-customer-management-software, /poss/pricing and the full sitemap; then the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io, whose Save Order request carries a per-order Customer object (name, email, phone, address, lat/long) but has no guest-account, saved-address, stored-instrument or reorder endpoint - and payment appears only as payment_type (e.g. COD) plus collect_cash. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Nothing states whether the Petpooja-hosted ordering site supports guest accounts, card tokenisation or one-tap reorder.

digital-upsell-engine differentiator

The menu push/fetch schema in the Online Ordering API blueprint (onlineorderingapisv210.docs.apiary.io) does carry merchandising fields - is_recommend ("Restaurant recommended item [1 - Recommended]", added 2024-10-23), item_tags [vegan, chef-special, new], markup_price strike-through and addongroups/addongroupitems - but these are static per-item flags and modifier groups, not order-context or history-based upsell suggestions at checkout. No attach-rate or suggestion-performance report is described on /poss/reports-and-analytics or /poss/restaurant-analytics-insights, which describe 40+/80+ reports without listing them. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Unresolved.

digital-scheduled-pacing

Save Order defines advanced_order ("Flag which says that placed order is advance or not. Value is Boolean either Y or N") with required preorder_date and preorder_time, and the spec states "for advance order the pre order date and time must be greater than or equal to current date and time of the system"; min_prep_time, urgent_order and urgent_time are also carried. So future/scheduled orders are a documented, first-class part of the order contract. Shortfall: nothing in the menu, get_store_status or update_store_status endpoints (which expose only an on/off store state plus a turn_on_time) or in the item_stock on/off endpoints exposes a per-time-slot or per-daypart cap on orders or items, so there is no documented mechanism that auto-closes a slot when the kitchen saturates - throttling is all-or-nothing store availability. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

digital-fulfillment-modes

Dine-in QR, website pickup/delivery and aggregator delivery are covered. Curbside with arrival check-in and mode-specific fee/prep timing are not documented. https://petpooja.com/poss/scan-and-order · retrieved 2026-08-01

digital-qr-table

Same add-on gating as above; capability claimed on a marketing page with no documentation of check-attachment semantics or conflict handling when the counter edits the same bill. https://petpooja.com/poss/scan-and-order · retrieved 2026-08-01 adversarially verified

digital-kiosk differentiator

First-party kiosk using the same POS menu and pricing with UPI/card payment and built-in printer. No accessibility-compliant UI documentation. https://petpooja.com/poss/self-service-kiosk · retrieved 2026-08-01

digital-group-ordering

'Different guests can order separately from the same table' onto one bill. No shareable link, per-person spend cap, or split-payment mechanic documented. https://petpooja.com/poss/scan-and-order · retrieved 2026-08-01

digital-catering-portal differentiator

Checked the outlet-type pages in the sitemap (fine-dine, QSR, cafe, food-court, cloud-kitchen, bakery, ice-cream, bar-and-brewery, pizzeria, large-chain), /poss/restaurant-website, /poss/table-reservation-manager, /poss/pricing and the Online Ordering API blueprint. The API's order model has a single order_type plus advance-order fields and no quote, proposal, deposit, lead-time or invoice/house-account construct; Petpooja publishes catering only as blog content (blog.petpooja.com/industry-business-guides/how-to-start-a-catering-business), which is editorial, not a product. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. No distinct catering ordering flow is described either way.

digital-voice-ai-phone differentiator

Checked /poss/restaurant-app-marketplace (the 11 first-party add-on services), /poss/self-service-kiosk and /poss/captain-ordering-app. Voice AI appears twice at Petpooja but never on the phone: the kiosk is "a touchscreen & voice recognition interface" for the walk-in guest, and the Captain app lets staff "add items for billing by AI voice recognition". The marketplace page states there are also "150+ third-party integrations", but that directory renders client-side and returned no partner list to a Googlebot fetch of /poss/restaurant-integrations, so I could not enumerate partners to check for a certified inbound-call agent. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Unresolved.

digital-drivethru-ai

Checked /poss/quick-service-restaurant-software, /poss/self-service-kiosk, /poss/token-management via the sitemap, /poss/restaurant-app-marketplace and the Online Ordering API blueprint. Drive-thru is not named anywhere on www.petpooja.com; the API's order_type has no drive-thru value and the only voice interfaces documented are the kiosk's voice recognition and the Captain app's staff voice input. Petpooja's markets (India, UAE, South Africa) have few drive-thru lanes, but that is inference, not evidence, and the pages checked are feature pages rather than an exhaustive channel list. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Unresolved.

digital-sms-ordering

Read /poss/restaurant-sms-service in full including its five-question FAQ: the product is outbound campaign SMS (promotional campaigns, birthday/anniversary scheduling, bill-print messages, system-generated coupon codes, customised sender ID, purchased SMS packages) with no inbound or conversational path. No WhatsApp or chat ordering product appears in the sitemap or in the 11-service marketplace catalogue, and the Online Ordering API blueprint has no messaging-channel order source. But a feature page plus its FAQ is not an exhaustive channel enumeration, and the 150+ third-party integration directory would not render for me, so text-to-order via a partner cannot be excluded. Unresolved.

digital-google-order differentiator

Checked /poss/online-order-management-software, /poss/restaurant-website, /poss/restaurant-integrations (client-side rendered; no partner list returned to a Googlebot fetch) and the Online Ordering API blueprint. The only marketplace-provisioning identifier in the entire order contract is ondc_bap, "an identifier to indicate if the order is from ONDC by passing the buyer app name" - India's Open Network for Digital Commerce, not Google. No Google Business Profile ordering-link provisioning, and no "Preferred by Business" handling, is described on any first-party page. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Unresolved.

digital-apple-business-connect

Checked /poss/restaurant-website, /poss/online-order-management-software, /poss/restaurant-app-marketplace and the Online Ordering API blueprint; Apple Business Connect, Apple Maps and Apple Maps place cards are not mentioned anywhere on www.petpooja.com (the only Apple-adjacent references in the record are OS support statements). The client-side integrations directory would not render for a Googlebot fetch, so I could not confirm the absence against a partner list. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Unresolved.

digital-loyalty-attach

CRM pools website, QR, Captain and in-house orders under one record; loyalty accrual and OTP redemption are described as POS-centric rather than in the web checkout. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

digital-subscriptions

Read /poss/restaurant-loyalty-program (the Loyalty Wallet product) in full including its FAQ. The wallet is a stored-value balance the operator or guest tops up "with multiple modes (Cash/ Card/ UPI)", with operator-set point allocation and expiry and OTP-gated redemption - a prepaid wallet, not a recurring-billing membership. No paid tier, delivery-fee-waiver subscription or per-period item entitlement is described there, on /poss/restaurant-customer-management-software or in the pricing add-on matrix, and the Online Ordering API has no recurring or entitlement construct. That is a feature page rather than an exhaustive product list, so this stays unresolved.

digital-promo-parity

Discounts and coupons configurable in POS and toggled on aggregator menus. Single-definition parity with channel eligibility is not documented; reviewers call the coupon engine weak. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-01

digital-guest-data-ownership differentiator

'Download the customer data as often as you want for free' - but the terms grant Petpooja a perpetual royalty-free licence to use that content and allow affiliate monetisation. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

digital-checkout-pci-sca

Checked https://www.petpooja.com/security - which is a vulnerability disclosure programme (safe harbour, scope, out-of-scope hosts) and carries no PCI DSS, SAQ or attestation statement at all - plus /privacy-and-policy (GDPR and IT Act 2000 framing only), /poss/restaurant-website ("Integrate Payment gateways with the website", gateway unnamed), /poss/self-service-kiosk (UPI QR, cards, pay-at-counter) and the Online Ordering API blueprint, where payment appears only as payment_type and collect_cash and no card data traverses the interface. Nothing states whether first-party checkout uses hosted fields or a hosted page, nothing addresses the PCI DSS 4.0 client-side script-integrity requirements, and 3DS is never mentioned (India's RBI regime mandates OTP/3DS at the gateway, but Petpooja does not document it). support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Unresolved.

digital-surcharge-transparency differentiator

Fee configuration held in the POS is propagated to connected ordering channels and itemised for guest display: the menu push/fetch schema defines packaging_applicable_on (NONE / ITEM / ORDER), packaging_charge and packaging_charge_type (PERCENTAGE / FIXED), and Save Order carries service_charge with sc_tax_amount, packing_charges with pc_tax_percentage and pc_gst_details, and delivery_charges with dc_tax_percentage and dc_gst_details, each GST block splitting liability between "vendor" and "restaurant". Shortfall: this is the India service-fee/packaging-charge model only. Neither the API nor any product page documents card surcharging or dual (cash-discount) pricing, guest-facing surcharge disclosure text, or any jurisdiction- or card-brand-level rule for where surcharging is prohibited. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

guest-loyalty-unified-profile

Consolidates online orders, Captain app, website orders and in-house orders 'into one data pool'. Dedup/merge behaviour on phone or email match is not documented. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

Every marketplace that relays an order into Petpooja calls Save Order, whose payload requires a Customer object - "email", "name", "address", "phone", "latitude", "longitude" - alongside the Restaurant and Order blocks, so a Swiggy/Zomato/Dineout/ONDC order does not land as an anonymous ticket; the identity fields are part of the contract. Shortfall: the contract carries no customer id, no match/merge or dedupe rule, and no link back to a Petpooja guest record, so attachment to a native profile rests on the CRM feature page's assertion that customer information "collected from online orders, the Captain app, website orders, and in-house orders" is synced "into one data pool" - a grade-C marketing statement, not documentation of profile matching. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

guest-loyalty-accrual-models

Pre-defined loyalty and cashback points allocated at billing, plus a top-up wallet. Visit/punch and spend-tier accrual models are not documented. https://petpooja.com/poss/restaurant-loyalty-program · retrieved 2026-08-01

guest-loyalty-tiers differentiator

Read /poss/restaurant-loyalty-program in full: the documented controls are pre-defined loyalty and cashback points, time-regulated reward campaigns, operator-set point allocation and expiry, multi-mode wallet top-up, OTP-gated redemption, a single wallet dashboard and blacklisting a customer from using their balance - a flat points/wallet scheme with no status level in it. Also checked /poss/restaurant-customer-management-software, which offers manual "customer labels", and the pricing matrix ("Petpooja loyalty" / "Loyalty Program" as a single add-on row with no tier sub-features). No rolling-window spend or visit thresholds, and no promotion/demotion behaviour, appear anywhere. These are feature pages rather than a configuration reference, so this stays unresolved rather than becoming a no.

guest-loyalty-offline-behavior differentiator

Petpooja markets "works offline, cloud-based software" on /poss/restaurant-billing-software, /poss/online-order-management-software and /poss/restaurant-customer-management-software, but none of those pages says what degrades during an outage. The loyalty mechanics that are documented on /poss/restaurant-loyalty-program are connectivity-dependent on their face - redemption is "OTP-regulated" via a POS-generated SMS to the registered mobile number, and point credits trigger an SMS - yet no page states whether lookup, accrual and redemption queue and reconcile or are simply blocked offline. The Online Ordering API blueprint covers aggregator relay only and says nothing about terminal offline behaviour. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Unresolved.

guest-loyalty-offer-stacking-rules differentiator

The prior partial rested on two legs and both fail. (1) Its named shortfall - 'that same complete field list contains no exclusive-vs-combinable flag' - was absence in the Online Ordering API v2.1.0 blueprint, which is an aggregator-facing projection that nowhere claims completeness and provably omits POS-side configuration, so it cannot establish what the discount engine does or does not expose. (2) The positive half was thinner than stated: the blueprint defines the field only as 'rank (string) - Discount rank', with no statement of what rank does, and the same document uses rank elsewhere purely for display order - 'categoryrank (string) - Category rank for ordering/stacking', 'addonitem_rank (string) - Addon item rank/order', 'rank (string) - Tax ranking'. Reading discount rank as order-of-application precedence is inference, not documentation, and this is a differentiator-weight claim. Re-searched for a stacking rule: Petpooja's glossary page lists 'Stackability settings: decide whether two offers can combine on one bill', but only inside a generic 'What a Good Coupon Management System Covers' list describing POS systems in general, with no statement that POSS implements it (blog.petpooja.com/glossary/coupon-management/, retrieved 2026-08-06). What is genuinely documented is scoping, not stacking: discountapplicableon [All/Categories/Items], discountcategoryitemids, discountordertype, discounthascoupon, and a per-item ignore_discounts flag ('0 - consider item for discount calculation, 1 - ignore item for discount calculation'). No first-party source states exclusivity, combinability, or a resolution rule for two discounts matching the same check. Unknown.

guest-loyalty-targeted-offers differentiator

'100+ types of customer labels' drive targeted campaigns and group discounts. Dynamic rule-based audiences over recency/frequency/spend are not documented. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

guest-loyalty-rfm-segmentation differentiator

Read /poss/restaurant-customer-management-software, which describes segmentation as operator work - "Create customer labels ... by simply categorising and labelling your customer pool the way you want" - alongside purchase-history tracking and special notes, and /poss/restaurant-sms-service, whose FAQ says the campaign feature "allows you to categorise your customers" and that you "create receivers' lists in advance". Nothing on those pages, on /poss/reports-and-analytics or on /poss/restaurant-analytics-insights names a computed lifecycle segment (new, regular, at-risk, lapsed, VIP) or a recency/frequency/monetary score. The reports pages advertise "40+"/"80+" reports without enumerating them, so an automatic segment cannot be excluded. Unresolved.

guest-loyalty-lifecycle-automation

'7+ unique campaign types' with automated birthday/occasion triggers. Lapsed win-back and first-visit thank-you as always-on automations are not documented. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

Native SMS campaigns and a dedicated SMS Service add-on. Native email campaigning is not documented. https://petpooja.com/poss/restaurant-sms-service · retrieved 2026-08-01

guest-loyalty-consent-management

Operators can 'restrict or block a customer from receiving promotional messages'. Per-channel consent capture with timestamp and source is not documented. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

guest-loyalty-10dlc-registration

The SMS Marketing FAQ does explicitly document the A2P registration the operator must complete before sending: "What are the requirements to start the Petpooja SMS service? To use Petpooja's SMS service, the customer needs to get their sender id & template id approved by TRAI (Telecom Regulatory Authority of India)", and a "customised sender ID for your restaurant" is a listed feature - so the registration obligation is disclosed rather than left implicit, and it is placed on the operator. Shortfall: the regime documented is India's TRAI/DLT sender-ID and template-ID approval, not US A2P 10DLC brand and campaign registration, which appears nowhere on www.petpooja.com even though the site's own enquiry form offers US and Canada dialling codes; Petpooja neither performs nor documents 10DLC registration. https://www.petpooja.com/poss/restaurant-sms-service · retrieved 2026-08-06

guest-loyalty-campaign-attribution differentiator

Checked /poss/restaurant-sms-service (campaign creation, scheduling and system-generated coupon codes at bill print, with no reporting described), /poss/restaurant-loyalty-program (a wallet/points dashboard, described as monitoring balances rather than campaign outcomes), /poss/reports-and-analytics and /poss/restaurant-analytics-insights, both of which advertise "40+" and "80+" reports plus a customisable dynamic-reports builder without listing the report catalogue. Coupon codes are issued per guest, so the raw material for attribution exists, but no page states that redemptions and resulting check totals are reported per campaign or offer. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io. Unresolved.

guest-loyalty-data-export-portability differentiator

I re-fetched the page. The sole supporting sentence is an FAQ line, "You can download the customer data as often as you want for free!" - no file format, no field list, no mention of transaction or order history, and no export procedure. The claim requires the full guest list AND transaction history including PII. Shortfall: only an unspecified "customer data" download is evidenced, and the terms cap post-termination retrieval at "within 2 days of such expiry or termination". https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-02 adversarially verified

guest-loyalty-cdp-event-api differentiator

Petpooja does document outbound push from the POS. The integration partner "must implement" a callback endpoint and pass it as callback_url on every Save Order; Petpooja then posts restID, orderID, status [-1=Cancelled, 1/2/3=Accepted, 4=Dispatch, 5=Food Ready, 10=Delivered], cancel_reason, minimum_prep_time, minimum_delivery_time, rider_name, rider_phone_number and is_modified. A rider_info webhook and partner-implemented item_stock / item_stock_off endpoints exist alongside it. Shortfall: the stream is order-status only, is delivered solely to the integration partner that relayed that specific order (there is no subscription or registration mechanism, and no events for website, Captain or in-store orders), and its payload contains no guest fields whatsoever - so a CDP or marketing platform such as Klaviyo cannot subscribe to guest or profile events. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

guest-loyalty-review-capture-routing differentiator

First-party Customer Feedback add-on collects post-transaction surveys. Score-based routing to private recovery vs public review sites is not documented. https://petpooja.com/poss/customer-feedback-management · retrieved 2026-08-01

guest-loyalty-referral-program

Checked /poss/restaurant-loyalty-program and its FAQ (points, cashback, wallet top-up, expiry, OTP redemption, virtual cards, blacklisting), /poss/restaurant-customer-management-software, /poss/restaurant-sms-service (which does issue system-generated coupon codes to a guest's registered number at bill print) and the pricing add-on matrix. No per-guest referral code or link, no attribution of a referred guest's first order and no two-sided reward is described; the coupon mechanic is campaign-issued, not referral-attributed. These are feature pages, not a configuration reference, so this remains unresolved rather than a no.

guest-loyalty-wallet-pass differentiator

Read /poss/restaurant-loyalty-program including the FAQ answer "Your customer can redeem points using messages sent by the POS system or their allotted virtual cards" - the two documented carriers are an SMS/OTP flow and a Petpooja-issued virtual card, and nothing describes what a virtual card is technically. Apple Wallet, Google Wallet, .pkpass and push-updatable balances are not mentioned there, on /poss/restaurant-customer-management-software, on the marketplace catalogue or in the sitemap. Because a "virtual card" could conceivably be a wallet pass and no page defines it, this cannot be resolved either way. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io.

guest-loyalty-privacy-rights-tooling

Read https://www.petpooja.com/privacy-and-policy in full. It asserts GDPR alignment and IT Act 2000 compliance, enumerates data-subject rights (access, rectification, erasure, restriction, portability), names a Data Protection Officer and a Grievance Redressal Officer, states a retention period after which data is anonymised, and routes requests through email - "To delete your account, You can email us at support@petpooja.com". Every one of those routes is Petpooja-to-its-own-account-holder and manual; nothing describes an operator-facing admin screen for fulfilling a restaurant guest's access or deletion request, or propagation of a deletion into CRM, loyalty wallet and SMS marketing records. A privacy policy is not an exhaustive description of the admin console, so this is unresolved rather than a no. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io.

guest-loyalty-redemption-fraud-controls

OTP verification at POS for redemption, point expiry dates, and blacklisting a customer's wallet. Velocity limits and employee self-redemption flagging are not documented. https://petpooja.com/poss/restaurant-loyalty-program · retrieved 2026-08-01

guest-loyalty-ai-offer-recommendation differentiator

The two shipped AI features Petpooja documents are both operational, not marketing: the Captain app lets staff "add items for billing by AI voice recognition" and offers "smart food recommendations" to the server at the table (/poss/captain-ordering-app, /poss/restaurant-app-marketplace), and the kiosk has a voice-recognition ordering interface. Nothing on /poss/restaurant-sms-service, /poss/restaurant-loyalty-program, /poss/restaurant-customer-management-software or the analytics pages claims AI/ML generation of offer content, audience selection or send timing - campaign audiences are described as operator-built label filters. support., help., kb., knowledge., docs., api., developer. and onlineordering.petpooja.com all return 404 or 500, so there is no help centre; the product surface is the 47 URLs in https://www.petpooja.com/sitemap.xml plus the Online Ordering API blueprint at onlineorderingapisv210.docs.apiary.io, and blog.petpooja.com carries editorial AI posts that are not product statements. Unresolved.

guest-loyalty-stored-value-gift

Loyalty Wallet holds stored value topped up by cash/card/UPI against the customer profile. Redeemability across all outlets of a brand is not documented. https://petpooja.com/poss/restaurant-loyalty-program · retrieved 2026-08-01

labor-clock-in-at-pos

Petpooja Payroll is a first-party product covering attendance and leave, and reports reference staff scheduling data. Clock-in at the POS terminal by PIN/badge is not documented. https://www.petpooja.com/ · retrieved 2026-08-01

labor-photo-punch-verification differentiator

Facial verification at punch is real: the Petpooja Payroll Face Scanner 'detects the face, runs an IR liveness check, verifies identity against the enrolled record, and logs the entry with an exact timestamp', feeding payroll in real time. Two shortfalls against the claim as worded. (1) It is a biometric-template system by design - the documented alternatives are 'NFC cards and passcodes', so no photo-only mode that stores no biometric template is offered, and no image is described as attached to the timecard row. (2) It is hardware for the separately sold Petpooja Payroll product (rebranded Attendo), not the POSS restaurant POS; the POSS plan matrix at petpooja.com/poss/pricing carries no attendance or time-clock line at any tier. https://blog.petpooja.com/people-payroll/petpooja-payroll-face-scanner-device/ · retrieved 2026-08-06

labor-geofenced-mobile-punch

Setup guide with real dashboard paths: 'go to Employees, then Attendance Permission. Toggle on Mobile Attendance for each target employee', and 'Standard mobile attendance captures a single GPS coordinate at punch-in and punch-out.' The payroll product page adds 'Authorise employees to punch-in for their shift based on the location assigned by their employer.' Shortfalls: this is the separately priced Petpooja Payroll product (base plan quoted at INR 8,000/year, with Geo Tracking a further INR 1,000/employee/year), not the POSS subscription; and the documented mechanism is location capture plus employer-assigned authorisation, with no published geofence radius, tolerance or block-on-out-of-fence behaviour. https://blog.petpooja.com/people-payroll/geo-tracking-works-petpooja-payroll/ · retrieved 2026-08-06

labor-offline-time-punch differentiator

Checked the four first-party places attendance behaviour is described: petpooja.com/payroll ('Instant data sync with software'; FAQ 'The sync is in real-time'), blog.petpooja.com/people-payroll/petpooja-payroll-face-scanner-device/ ('Real-time data sync ... no waiting for the end-of-day sync, no manual upload, no lost entries during a network blip'), blog.petpooja.com/people-payroll/geo-tracking-works-petpooja-payroll/, and blog.petpooja.com/people-payroll/how-petpooja-payroll-works/. All describe device-to-cloud sync as instantaneous; none states what happens to a punch taken while the device or phone is offline, and none documents duplicate handling on reconnect. Petpooja's published offline claims (POSS 'works perfectly well, even in offline mode', Captain App 'up to 5 days of offline operation before a sync is required', per blog.petpooja.com/industry-business-guides/petpooja-captain-ordering-reduces-order-errors/) are about order capture on the POS, not time punches on the separate payroll product. www.petpooja.com/sitemap.xml has no attendance page beyond /payroll and support./help./kb.petpooja.com do not resolve, so there is no admin guide to check.

labor-granular-rbac

'User rights management' regulates staff access and unlimited user rights ship on every tier. Grantability per discrete action per role per location is not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

labor-manager-override-audit

Reports cover bill modifications, discounted and cancelled orders, and staff actions. An immutable, queryable approver-attributed audit trail is not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

labor-native-scheduling differentiator

Staff scheduling data appears in reports and the separate Petpooja Payroll product handles attendance/leave. Schedule building and publishing inside the POS platform is not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

labor-demand-labor-forecast differentiator

blog.petpooja.com/operations-workflows/ai-sales-forecasting-restaurants-guide/ discusses forecasting driving 'how many hands each shift really needs', but it is written as category education about AI forecasting in general ('it usually sits inside the POS or restaurant software you already run') and never asserts that Petpooja ships one. blog.petpooja.com/procurement-cost-control/petpooja-ai-features-help-restaurants-decide-better/ enumerates Petpooja's AI features as Best Match, live price comparison, AI invoice scanning and automatic inventory sync - all purchasing-side, none staffing. The staffing side lives in the separate Petpooja Payroll product, whose documented calculation inputs (blog.petpooja.com/people-payroll/how-petpooja-payroll-works/) are working days, leave, shift timings and overtime hours, with no sales feed from POSS. www.petpooja.com/poss/pricing lists no labour or scheduling module in any tier. Unresolved rather than absent: no scheduling admin guide is published anywhere on petpooja.com.

labor-realtime-labor-percent differentiator

The POSS reporting surface is described on www.petpooja.com/poss/reports-and-analytics (single-dashboard monitoring, tax reporting, user-rights/bill-modification reports, head-office module) and quantified as '80+ Reports' in every tier on www.petpooja.com/poss/pricing; neither names a labour-cost metric, and the pricing matrix contains no attendance or payroll line at any tier. Wage and hour data sits in the separately sold Petpooja Payroll product (www.petpooja.com/payroll), which is documented as consuming attendance, shifts, leave and overtime and producing salary reports - nothing in blog.petpooja.com/people-payroll/petpooja-payroll-features/ or /how-petpooja-payroll-works/ describes POS sales flowing into it, which is what a live labour-percent view would require. No manager-view or live-KPI screen is documented on any host; there is no help centre (support./help./kb.petpooja.com all fail to resolve) to check further.

labor-overtime-prevention differentiator

The Easy Payroll feature list says 'Enforce overtime & late entry rules with a penalty', and blog.petpooja.com/people-payroll/petpooja-payroll-features/ adds that 'Attendance is then evaluated against the assigned shift timings. Late arrivals, early departures, overtime: all captured automatically.' So a configured overtime threshold exists. The missing half is the one the claim is about: every documented enforcement is retrospective, applied when salary is calculated, and no warning, prompt or block is documented at the moment of clock-in - the face scanner, biometric and mobile punch flows are all described as recording the punch and syncing it, with no eligibility check. Also a separate SKU from the POS. https://www.petpooja.com/payroll · retrieved 2026-08-06

labor-break-compliance-by-state differentiator

Read the compliance content of the only product that touches labour rules: www.petpooja.com/payroll (leave types, paid/unpaid leave, approval mechanism, shift creation including overnight and alternate week-offs) and blog.petpooja.com/people-payroll/petpooja-payroll-features/, whose compliance FAQ enumerates 'Provident Fund, Employee State Insurance, Professional Tax, and Labour Welfare Fund deductions'. Meal or rest break rules, per-state or per-jurisdiction rule sets, break attestation prompts and missed-break premium pay appear nowhere in that content, nor in the 800 URLs of blog.petpooja.com/post-sitemap.xml (grepped for break/meal/rest/attestation). This is a jurisdiction-shaped question for a product sold into India, where no analogous per-state meal-break premium regime exists, but Petpooja publishes no supported/unsupported statement either way, so the honest answer is unresolved rather than absent.

labor-fair-workweek-support

The whole scheduling surface Petpooja documents is in the payroll product: 'Multiple shift creation & assignment', '24-hour & overnight shifts timings', 'Alternate week-off assignment' (www.petpooja.com/payroll), and 'administrators define shift schedules and assign employees to them' (blog.petpooja.com/people-payroll/petpooja-payroll-features/). There is no notion of a published schedule, an advance-notice deadline, or an employer-initiated change record, which are the objects predictability-pay tracking would have to attach to. Grepped all 800 posts in blog.petpooja.com/post-sitemap.xml for fair-workweek / predictive / predictability / advance-notice: no hits. Predictive-scheduling ordinances are a US municipal regime and Petpooja is an India-market product, but the vendor makes no statement of support or non-support, so this stays unresolved.

labor-minor-labor-rules

Checked the two places a rule of this kind would have to live. Scheduling: www.petpooja.com/payroll documents shift creation/assignment, overnight shifts and alternate week-offs, with no employee-attribute-driven constraint. Clock-in: the face scanner, biometric and mobile-attendance flows (blog.petpooja.com/people-payroll/petpooja-payroll-face-scanner-device/, /geo-tracking-works-petpooja-payroll/) all record and sync the punch with no eligibility evaluation described. The employee master is described only in terms of salary structure, shift, leave balance and department/designation (blog.petpooja.com/people-payroll/petpooja-payroll-features/) - no date-of-birth-driven rule set. Grepped the 800-post blog sitemap for minor/child/age-based/school-day: no product content. No supported/unsupported statement exists, so unresolved.

labor-tip-pooling-rules

Searched for a tip data model in the three places one would appear. (1) The Online Ordering API blueprint retrieved from onlineorderingapisv210.docs.apiary.io/api-description-document (Save Order request attributes: taxes, discounts, delivery and packing charges, payment_type, collect_cash) has no tip or gratuity attribute anywhere in its 116KB of schema. (2) The payroll salary model (blog.petpooja.com/people-payroll/petpooja-payroll-features/, /how-petpooja-payroll-works/) is built from working days, leave, overtime, salary structure, PF/ESIC/PT/LWF and salary advances - no tip component, and the vendor states salary disbursal itself is out of scope. (3) Grepped all 800 posts in blog.petpooja.com/post-sitemap.xml: every 'tips' hit is advice-article usage ('menu tips', 'marketing tips'), none about gratuity. The API schema is exhaustive only for the aggregator order path, not for dine-in billing, so this is unresolved rather than a documented absence; there is no help centre on any petpooja.com subdomain to check dine-in billing behaviour.

labor-tip-distribution-audit-trail

The audit-trail machinery Petpooja does document is per-employee and exportable but never mentions tips: user-rights reports on 'bill modifications, discounted/cancelled orders, cash drawer operations' (www.petpooja.com/poss/reports-and-analytics), the KOT modification log with 'what changed, who changed it, and when', and Report #82 Captain Performance showing sales per captain, order count and item mix (blog.petpooja.com/industry-business-guides/petpooja-captain-ordering-reduces-order-errors/). None of these carries a tips-received, contributed or distributed figure. The Save Order schema in the API blueprint at onlineorderingapisv210.docs.apiary.io/api-description-document has no tip attribute, and the payroll product's per-employee records are attendance, leave, overtime, advances and statutory deductions. No first-party statement of support or non-support exists, so unresolved.

labor-qualified-tips-w2-reporting differentiator

US W-2 Box 12 code TP / Box 14b and Treasury tipped-occupation codes are outside Petpooja's operating geography (India, UAE, South Africa); nothing of the kind is documented.

labor-native-payroll differentiator

Petpooja Payroll is a first-party product for attendance, leave and payroll management. Statutory tax filing and direct-deposit disbursement by Petpooja are not documented. https://www.petpooja.com/ · retrieved 2026-08-01

labor-payroll-export-formats

FAQ: 'Payroll reports, attendance summaries, and payslips can all be exported from the web dashboard. These reports can be shared with accountants or integrated into external bookkeeping systems.' www.petpooja.com/payroll adds '6+ industry-standard reports and unlimited customisable reports', 'download reports in excel or export to google sheets'. Shortfalls against the claim as worded: the export targets are generic spreadsheet/bookkeeping formats, not a documented format or direct integration for any named payroll provider - no provider is named on any Petpooja host; and tips are not a tracked field anywhere in the payroll model, so tips cannot be exported. Note also that Petpooja is itself the payroll engine here (PF/ESIC/PT/LWF, payslips), which is why no third-party payroll connector exists, but the claim asks about provider-format export and that is not met. https://blog.petpooja.com/people-payroll/petpooja-payroll-features/ · retrieved 2026-08-06

labor-shift-swap-workflow differentiator

www.petpooja.com/payroll documents the employee app precisely: staff can 'access their shifts, leaves & daily attendance records' and 'submit their leave requests & punch-in time corrections whenever required', with the owner app providing 'hassle-free approvals of leave & attendance adjustments'. blog.petpooja.com/people-payroll/petpooja-payroll-features/ describes shift assignment as an administrator action. So the self-service-plus-approval plumbing exists but the two request types documented are leave and punch correction; neither a swap between employees nor an open-shift pool appears, and there is no mention of overtime or role-eligibility checks inside any approval. I am leaving this unknown rather than scoring it, because the employee-app request list on a marketing page is not an exhaustive enumeration of the app's screens, and no admin guide for the app is published (support./help./kb.petpooja.com do not resolve).

labor-digital-onboarding-i9

W-4/I-9/E-Verify are US-specific and irrelevant to Petpooja's markets; no equivalent onboarding documentation exists.

labor-server-performance-metrics differentiator

Reports cover staff actions and scheduling data. Per-server average check, attachment rate and void/comp rate are not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

inventory-recipe-bom-costing

'Multi-stage recipe management' implies sub-recipes with consumption tracked across production stages. Automatic plate-cost recalculation on ingredient price change is not documented. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01

inventory-unit-conversion-yields

Read the full inventory surface Petpooja publishes: www.petpooja.com/poss/restaurant-inventory-management-software (central kitchen module, raw material management with low-stock alerts, 'Multi-stage recipe management ... automatically deduct your stock when used ... consumption rate at every stage', purchase order management), www.petpooja.com/poss/purchase-manager and its setup guide blog.petpooja.com/industry-business-guides/petpooja-purchase-manager-features-setup/ (vendor rate cards uploaded in Excel, auto stock sync on receipt), and blog.petpooja.com/industry-business-guides/ultimate-guide-to-restaurant-inventory-management/. Multi-stage recipes and semi-finished raw materials imply an internal conversion model, but no page states that an item carries distinct purchase / recipe / count units with explicit conversion factors, and no yield or raw-to-usable waste percentage field is described anywhere. Wastage is only ever discussed as a recorded event, not as a yield factor applied to conversion. No item-master schema is published (the only API blueprint, onlineorderingapisv210.docs.apiary.io/api-description-document, covers menu and orders, not raw materials), so this cannot be settled from public sources.

inventory-theoretical-vs-actual differentiator

Petpooja describes a Variance Report that 'checks units used against units sold' and 'gives you the difference between the ideal stock that should be available at the end of the day and the stock that actually remained', sitting alongside a Consumption Report covering 'stock count, purchases, and the inventory returned to the vendor or wasted'. The theoretical side is real: the POS 'automatically deduct[s] your stock when used' from uploaded item-wise recipes (www.petpooja.com/poss/restaurant-inventory-management-software). Shortfalls: the description appears in an educational listicle rather than a report specification; the variance period is fixed at end-of-day rather than a user-defined count period; and nothing states the variance is expressed per item in currency as well as units - the only currency framing in the article attaches to the separate Waste Report. https://blog.petpooja.com/procurement-cost-control/bar-inventory-reports/ · retrieved 2026-08-06

inventory-realtime-depletion differentiator

The page claims recipe-driven deduction - "Upload your item-wise recipe in the software & let the smart POS look after your consumption rate", "automatically deduct your stock when used", plus "low stock" alerts. That is a marketing claim with no timing stated. Shortfall: nothing distinguishes near-real-time depletion from an end-of-day batch, modifier-driven depletion is nowhere documented, and the Inventory Module starts at the Growth tier. Petpooja publishes no admin guide or help centre against which any of this could be confirmed. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-02 adversarially verified

inventory-86-auto-sync differentiator

I re-fetched the page. What it actually offers is an operator action, not automation: "Toggle your online menu ON/OFF basis of stock availability" and "manage the availability of menu items both for dine-in & online menu". The online-order page is the same - "toggle any online menu item On or Off as per your inventory". Shortfall: nothing documents an automatic 86 when a component ingredient hits zero or a configured threshold, nothing documents the change reaching Swiggy/Zomato menus automatically, and the Inventory Module is absent from the Core tier on the vendor's own pricing matrix. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-02 adversarially verified

inventory-count-modes

The counting workflow Petpooja publishes amounts to two things: 'check day-end inventory with a simple click' via the Inventory App (blog.petpooja.com/industry-business-guides/ultimate-guide-to-restaurant-inventory-management/) and a perpetual-inventory concept that 'accounts for the available stock after each purchase' (blog.petpooja.com/procurement-cost-control/bar-inventory-reports/). Neither an ad-hoc partial count nor a scheduled recurring cycle count is described anywhere, and no page states whether each count is retained as its own history row with its own variance or overwrites the prior figure - the Variance Report is described as an end-of-day comparison, which is suggestive but not a statement about count history. www.petpooja.com/poss/restaurant-inventory-management-software and /poss/purchase-manager say nothing further. There is no inventory admin guide on any petpooja.com subdomain to settle it.

inventory-mobile-count-offline

The only first-party description of a mobile inventory tool is blog.petpooja.com/industry-business-guides/ultimate-guide-to-restaurant-inventory-management/: 'with the help of the application, you can check on inventory availability, set low-stock alerts, create inventory delivery routes to various outlets, & check day-end inventory with a simple click'. That does not establish that counts are entered on the device, and it says nothing about barcode or QR scanning or about behaviour with no connectivity. Petpooja's published offline claims are elsewhere and are about order capture, not counting: 'works perfectly well, even in offline mode' on www.petpooja.com/poss/restaurant-billing-software and 'up to 5 days of offline operation' for the Captain App (blog.petpooja.com/industry-business-guides/petpooja-captain-ordering-reduces-order-errors/). The marketing line about stock-keeping 'in under 15 minutes' on www.petpooja.com/poss/restaurant-inventory-management-software still does not describe the tool. No app store listing or admin guide is linked from any Petpooja page, so this is unresolved on all three sub-conditions.

inventory-vendor-catalogs-edi differentiator

Raise and accept purchase-order tickets directly with suppliers, with per-supplier frequently-ordered tracking and e-way bills auto-uploaded to GST portals. No named broadline distributor catalogues. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01

inventory-invoice-ocr differentiator

The AI feature table lists 'AI invoice scanning - Reads a photographed bill into your system', and the article instructs 'Start photographing supplier invoices so the AI reads each one into a purchase entry, instead of anyone typing it', with the resulting purchase entries feeding food-cost and margin figures and syncing stock to POSS. Shortfalls: only the photo path is documented - no PDF upload and no invoice-by-email ingestion; the extracted fields are never enumerated, so line-item detail (item, quantity, unit, price) is asserted only by implication; and the feature sits in Petpooja Purchase, whose pricing the same article explicitly declines to state ('Pricing depends on the plan and product'), while the free Purchase Manager add-on documented at www.petpooja.com/poss/purchase-manager lists five core capabilities that do not include invoice scanning. https://blog.petpooja.com/procurement-cost-control/petpooja-ai-features-help-restaurants-decide-better/ · retrieved 2026-08-06

inventory-price-change-alerts differentiator

'Track your inventory purchases, recipe costs, and raw material price trends with Petpooja's restaurant inventory software' - so per-item purchase price history exists. The Purchase Manager add-on adds a live price dimension: 'Rates refresh in real time, so you see the actual price at the moment you are ordering, not yesterday's rate card', with prices updating in-cart before order confirmation (www.petpooja.com/poss/purchase-manager). Shortfall: both mechanisms are pre-purchase comparison and retrospective trend viewing. No configurable threshold, and no alert fired when a received or invoiced price exceeds the prior or contracted price, is documented anywhere - the alerting Petpooja does document on the inventory side is low-stock and expiry-stock alerts, not price alerts. https://www.petpooja.com/poss/reports-and-analytics · retrieved 2026-08-06

inventory-par-auto-suggest differentiator

Low-stock alerts and frequently-ordered-item tracking per supplier per outlet. Par-versus-on-hand suggested PO quantities and forecast-driven pars are not documented. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01

inventory-waste-logging

Damaged-stock returns exist within the central-kitchen module and the vendor claims 65% wastage reduction. A reason-coded waste log with separate waste-cost reporting is not documented. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01

inventory-transfers

Multi-outlet stock movement between locations with delivery route creation, managed from a single dashboard. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01

inventory-commissary

Dedicated central-kitchen module with request/supply between outlets and damaged-stock returns; included on all pricing tiers. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01

inventory-lot-traceability

Read the receiving and production chain Petpooja publishes: purchase order raise/accept and 'inward stock receipts' (www.petpooja.com/poss/restaurant-inventory-management-software), automatic stock update on receipt via Purchase Manager (www.petpooja.com/poss/purchase-manager), central kitchen dispatch of semi-finished raw materials to outlets with 'records of the goods sent, sales & inventory conversion rate for every single outlet' (blog.petpooja.com/industry-business-guides/ultimate-guide-to-restaurant-inventory-management/), and multi-stage recipe production. Transfers are tracked at item level throughout; no lot, batch or supplier-lot identifier is captured at receiving in any description, and no recall or trace report appears in the report types listed at blog.petpooja.com/procurement-cost-control/bar-inventory-reports/. Grepped the 800-post blog sitemap for lot/batch/traceab/recall: only unrelated usages. No inventory schema is published, so unresolved rather than absent.

inventory-shelf-life-expiry

'Low & expiry stock alerts: You can set low stock alerts and expiry stock alerts on every ingredient in your restaurant so that you can be notified in advance.' That is a first-party statement of a per-ingredient expiry alert fired ahead of the event, which is the alert half of the claim. Shortfalls: the alert is described as a per-ingredient setting, not as tracking of a date captured at receiving or on a prepped batch - no receiving-time expiry date field or prep/production date is documented anywhere, including www.petpooja.com/poss/restaurant-inventory-management-software and the purchase flows; and no expiring-soon report appears in the inventory report types Petpooja lists. Expiry is otherwise mentioned only as a wastage reason in the Waste Report. https://blog.petpooja.com/operations-workflows/must-try-features-petpooja-pos/ · retrieved 2026-08-06

inventory-bar-partial-bottle

Read both bar-specific first-party pages in full. www.petpooja.com/poss/bar-and-brewery-pos-software frames the problem ('you and your staff must be spending hours every single day counting bottles of liquors and taking bar inventory manually') and offers multi-counter billing and liquor reporting, but describes no counting unit. blog.petpooja.com/procurement-cost-control/bar-inventory-reports/ lists eight bar report types (consumption, variance, waste, end-of-day, discounted orders, item-wise tax, recipe costing card, perpetual inventory form) and closes with a rhetorical line that 'even the remaining quarter of that Bombay Sapphire is accounted for' - a marketing flourish, not a described mechanism. Nothing on either page, or in the peg/measure sense anywhere on blog.petpooja.com, documents scale or weight integration or a fractional-bottle count unit. No hardware compatibility list exists on any Petpooja host to check for scales.

inventory-cogs-gl-export

www.petpooja.com/poss/restaurant-app-marketplace claims '150+ third-party integrations for online orders, loyalty programs, payments, accounting, etc.' but names not one accounting system; its own catalogue on that page lists eleven first-party add-ons (wireless calling, kiosk, scan and order, Purchase Manager, digital display, captain app, KDS, token, table reservation, website, loyalty, SMS, feedback, reconciliation, dynamic reports) with no accounting connector among them, and the page's integration logo grid loads client-side and returned nothing to a Googlebot or browser user agent. www.petpooja.com/poss/restaurant-integrations renders its partner grid client-side too and yielded only prose. The one place Tally and SAP appear is blog.petpooja.com/operations-workflows/restaurant-accounting/, and it is generic advice to the reader ('Look for a POS system that also provides integrations with the industry's best accounting software like Tally or SAP'), not a claim about Petpooja. No GL account mapping per item category, and no COGS or AP export format, is described on any host. A directory that names nothing cannot support a no, so unresolved.

inventory-native-not-partner differentiator

Score survives but the citation is wrong and the tier claim is fabricated-by-inference. The pricing page's visible matrix contains no "Inventory Module" or "Menu Management" row at all, so "ships in the Growth and Scale tiers" is unsupported. The correct support is the inventory page itself, which sits under the POSS product nav alongside Billing/Online ordering/Reporting and claims item-wise recipes, automatic deduction, central kitchen, inter-outlet transfers with delivery routes, supplier POs and GST e-way-bill upload. Native: yes. Tier placement: unknown. https://petpooja.com/poss/restaurant-inventory-management-software · retrieved 2026-08-01 adversarially verified

inventory-menu-margin-linkage differentiator

Both inputs are documented separately. Cost side: recipe costing with 'the exact cost of each recipe based on the precise amount and price of each ingredient', a Recipe Costing Card report, and 'recipe costs' tracked in the inventory module (www.petpooja.com/poss/reports-and-analytics, blog.petpooja.com/procurement-cost-control/bar-inventory-reports/). Sales side: item-wise sales and item mix, including in Report #82 Captain Performance. The join is what is missing: no first-party page describes a contribution-margin-per-menu-item report, and no page describes a configurable margin threshold or a flag raised when ingredient cost changes push an item below it. The nearest statement is blog.petpooja.com/procurement-cost-control/petpooja-ai-features-help-restaurants-decide-better/, which says accurate purchase entries mean 'your food cost and margin numbers hold up' and that margin 'lands in the P&L you read from your POS' - a P&L, not a per-item margin report. The 80+ report catalogue is not published in full anywhere, so this cannot be settled.

reporting-realtime-dashboard

Cloud single-dashboard monitoring accessible off-premise. A dedicated owner mobile app for live sales is not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reporting-eod-closeout

Day-end reports in under 5 minutes covering sales, payment status, tax/income summaries and cash-drawer operations. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reporting-pmix-modifier-level

Item-wise sales and consumption reporting is documented. Modifier-level PMIX with daypart and revenue-center filters is not. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reporting-comps-voids-audit

'Detailed reports on bill modifications, discounted/cancelled orders, cash drawer operations.' Reason codes and named approver attribution are not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reporting-cash-over-short

Cash-drawer operation reporting exists. Explicit over/short per drawer, shift and employee against expected cash is not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reporting-labor-productivity

The claim requires actual clocked hours from the POS time clock. The POSS plan matrix at www.petpooja.com/poss/pricing enumerates Cloud Billing, Inventory Module, 80+ Reports, in-built CRM, menu management, unlimited terminals and user rights, central kitchen and multi-terminal billing, with add-ons for KDS, captain app, website, loyalty, token, feedback, QR ordering and dynamic reports - no attendance, time-clock, scheduling or labour module at any tier. Clocked hours live in the separately sold Petpooja Payroll product (www.petpooja.com/payroll), whose documented calculation inputs are attendance, shifts, leave and overtime, with no sales feed described in blog.petpooja.com/people-payroll/how-petpooja-payroll-works/ or /petpooja-payroll-features/. www.petpooja.com/poss/reports-and-analytics names no labour metric. I could not enumerate the 80+ POSS reports - Petpooja publishes no report catalogue and has no help centre (support./help./kb./developer.petpooja.com all fail) - so a per-hour or per-employee labour report cannot be ruled out, only left unresolved.

reporting-server-scorecards differentiator

'Report #82 in Petpooja POSS is the Captain Performance Report. It shows sales per captain from the captain app, broken down by order count, item mix, and total value', and is used to spot 'which captains have higher cancellation rates, which ones use modifiers consistently, and which ones drive more upsell'. Average check is derivable from total value over order count but is not a stated column. Shortfalls: no items-per-check figure, no attachment rate for named categories, and no tip percentage - tips are not a tracked field anywhere in Petpooja's published model. Scope shortfall too: the report reflects orders taken through the Captain App, which the same page's FAQ says 'works only with Electron POS and Local POS. It is not available on Petpooja Lite or the basic Android POS', and the captain app is an add-on rather than a bundled module on www.petpooja.com/poss/pricing. https://blog.petpooja.com/industry-business-guides/petpooja-captain-ordering-reduces-order-errors/ · retrieved 2026-08-06

reporting-channel-profitability differentiator

Same source, same problem: marketing page, not documentation, and the module behind it is a priced add-on. Commission/margin-per-aggregator breakout is a claim, not a documented report spec. https://petpooja.com/poss/online-order-reconciliation · retrieved 2026-08-01 adversarially verified

reporting-multiloc-drilldown differentiator

Head-office module shows all outlets on one dashboard with city-wise and zone-wise grouping. Drill-down from group total to individual transaction is not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reporting-custom-report-builder differentiator

A 'Dynamic Reports' marketplace add-on is listed under Analytics. Dimension/measure/filter self-service builder behaviour is not documented. https://petpooja.com/poss/restaurant-app-marketplace · retrieved 2026-08-01

reporting-scheduled-delivery

Automated report alerts delivered by email on a configured basis. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reporting-raw-warehouse-export differentiator

Retrieved the full API blueprint at onlineorderingapisv210.docs.apiary.io/api-description-document (the docs page itself renders client-side; the description document returns the complete source). Its endpoint list is Push Menu, Fetch Menu, Save Order, Order Callback, Update Order Status, Rider Info webhook, item stock on/off, get/update store status - nothing that emits transaction-level data in bulk, and no S3/SFTP/warehouse destination anywhere. On the reporting side, www.petpooja.com/poss/restaurant-analytics-insights (Dynamic Reports add-on) offers 'download your reports to have them on the go' and blog.petpooja.com/operations-workflows/restaurant-business-dynamic-reports/ says you can 'see, analyse & even export all your data with a single click' - manual export, no schedule, no destination. I am not scoring a no on this: the blueprint is exhaustive only for the aggregator online-ordering integration, not for the platform's whole API surface, and www.petpooja.com/sitemap.xml exposes no data-platform or export page to check.

reporting-public-api differentiator

Not documented publicly: no developer portal resolves (docs.petpooja.com 500s) and the integrations page offers only a contact form for prospective partners. https://petpooja.com/poss/restaurant-integrations · retrieved 2026-08-01

reporting-webhooks differentiator

Petpooja's Online Ordering API v2.1.0 blueprint (the rendered docs page is client-side only; this is the source document it loads) documents genuine outbound webhooks to a customer-supplied endpoint: 'Order Callback Request/Response [/callback] - Online order integration partner must implement this endpoint to allow PoS partner to notify about order status updates', with the endpoint passed per order as callback_url and a payload carrying restID, orderID, status (-1 cancelled, 1/2/3 accepted, 4 dispatched, 5 food ready, 10 delivered), cancel_reason, prep/delivery times, rider details and is_modified. Petpooja also pushes the full menu to an integrator endpoint after every change and calls integrator-hosted item-stock endpoints. Shortfalls: the callback request's documented attribute list contains no signature, HMAC, token or app_key field, so there is no payload verification (the app_key/app_secret/access_token triple appears only on inbound calls TO Petpooja); no retry, backoff or delivery-guarantee behaviour is stated anywhere in the document; the events are order-lifecycle only, with no payment events (payment appears solely as a payment_type string on the inbound order); and access is scoped to registered integration partners - 'Credentials for both staging and production environment will be provided by petpooja team' - not to any merchant with an endpoint. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

reporting-api-not-upcharged differentiator

Re-checked with the primary source this time rather than the third-party listing. The Petpooja Online Ordering API blueprint (onlineorderingapisv210.docs.apiary.io/api-description-document) says only 'Access to developer account of staging/production: https://developerapi.petpooja.com/. Credentials for both staging and production environment will be provided by petpooja team' - no price, no plan requirement, no revenue share, and developerapi.petpooja.com returns 403 without credentials. The vendor plan matrix at www.petpooja.com/poss/pricing lists no API or integration line item at Basic, Core, Growth or Scale; API access appears in neither the included features nor the add-ons list, so the pricing page does not gate it and does not include it either. www.petpooja.com/poss/restaurant-integrations only invites prospective partners to 'contact us'. The earlier refutation stands - API Integration is not Scale-only on the SoftwareSuggest listing - and no first-party statement of API packaging or cost exists, so unknown. adversarially verified

reporting-tier-paywall differentiator

Re-reading the vendor's own tier matrix refutes the unqualified yes: "80+ Reports" and in-built CRM do sit on Core, but "Dynamic reports" is a Scale-tier-only row, and the Inventory Module and Menu management start at Growth - so stock, COGS and menu-driven reporting are not on the entry plan. Shortfall: Petpooja publishes no report catalogue, so whether the Core "80+" set includes PMIX, labour-vs-sales, a comps/voids audit or multi-outlet comparison is undocumented, and the top of that range is explicitly paywalled. https://petpooja.com/poss/pricing · retrieved 2026-08-02 adversarially verified

reporting-history-retention differentiator

The Dynamic Reports FAQ answers 'What is the time range to know my data in dynamic reports?' with 'you can view your business data going back decades as long as it has been recorded in the system' - an assertion of no retention limit that comfortably exceeds 24 months if taken at face value. Shortfalls: it is a marketing FAQ for a priced add-on (Dynamic Reports is listed under 'Advanced features' on www.petpooja.com/poss/pricing and under Add-ons/ANALYTICS on this page and the marketplace), not a documented retention policy; it says nothing about transaction-level granularity as opposed to aggregates; and no retention window, truncation behaviour or archive-retrieval fee is stated for the standard 80+ report set that Core, Growth and Scale subscribers get without the add-on. https://www.petpooja.com/poss/restaurant-analytics-insights · retrieved 2026-08-06

reporting-anomaly-alerts differentiator

Automated report alerts and low-stock alerts exist. Operator-configured metric thresholds or deviation-from-pattern alerting is not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reporting-nl-query

blog.petpooja.com/procurement-cost-control/petpooja-ai-features-help-restaurants-decide-better/ is the vendor's own account of what its AI does, and it states plainly 'The AI here is not a chatbot or a robot. It works quietly on the inputs to a decision', then tables the four features as Best Match, live price comparison, AI invoice scanning and automatic inventory sync - none of which answers ad-hoc questions over the operator's own data. The other AI mention on any Petpooja host is an upsell recommendation engine in the captain app. Against that, the analytics surface (www.petpooja.com/poss/restaurant-analytics-insights) is a customisable dashboard and chart builder, explicitly not a query interface. I stopped short of scoring a no: that AI article is a features roundup, exactly the source type that cannot carry an enumeration argument, and its 'not a chatbot' line is framing rather than a support statement of non-support. No release-notes or changelog page exists on www.petpooja.com/sitemap.xml to check for a newer assistant.

reporting-guest-cohorts differentiator

CRM tracks purchase history and supports 100+ customer labels. New-versus-returning counts, frequency and lifetime-spend cohorts are not documented as computed reports. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

reporting-sales-forecast differentiator

blog.petpooja.com/operations-workflows/ai-sales-forecasting-restaurants-guide/ looks like a hit but is not one: it describes the category ('it is not a separate app you buy; it usually sits inside the POS or restaurant software you already run'), never says Petpooja provides it, and its only Petpooja reference is that restaurants 'on Petpooja' who plan against a forecast waste less. The vendor's own AI inventory - blog.petpooja.com/procurement-cost-control/petpooja-ai-features-help-restaurants-decide-better/ - lists Best Match, live price comparison, invoice scanning and stock sync, all backward- or present-looking, and frames the P&L and food-cost outputs as reports. www.petpooja.com/poss/reports-and-analytics and /poss/restaurant-analytics-insights describe historical dashboards and customisable report building with no projection. No forward-looking report is named anywhere, but the 80+ POSS report catalogue is unpublished and there is no help centre, so unresolved.

reporting-tip-tax-compliance

Checked the three surfaces this report would draw from. Order data: the Save Order schema in the API blueprint at onlineorderingapisv210.docs.apiary.io/api-description-document itemises taxes, discounts, delivery charge, packing charge, payment_type and collect_cash, with no tip or gratuity attribute, and its 2022-2025 changelog adds none. Payroll: blog.petpooja.com/people-payroll/petpooja-payroll-features/ and /how-petpooja-payroll-works/ build salary from working days, leave, overtime, salary structure, PF/ESIC/PT/LWF and advances - no tip component or tip income line on the payslip. Reporting: www.petpooja.com/poss/reports-and-analytics offers 'easy tax reporting' and item-wise tax reports (per blog.petpooja.com/procurement-cost-control/bar-inventory-reports/) built on GST, not on tip liability. The tax framing throughout is Indian GST, where tips are not a payroll-tax reporting object as they are in the US. No first-party statement of support or non-support exists, and there is no help centre on any petpooja.com subdomain, so unresolved.

multi-location-org-hierarchy

Head-office module with city-wise and zone-wise groupings above individual outlets gives at least three scoped levels for reporting. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

multi-location-central-menu-publish

'Update the entire menu of your restaurant in just one single click' plus head-office oversight. Targeted multi-outlet publish with version history is not documented. https://petpooja.com/poss/restaurant-menu-management-software · retrieved 2026-08-01

multi-location-local-override-policy differentiator

"A POS built for multiple outlets lets you set item availability and price per outlet or per channel, from one dashboard... Head office stays in control, and each manager only sees what applies to their branch", with the worked example of one brand keeping a chicken biryani at two different prices in two outlets. The menu-management guide adds that outlets "inherit" a master menu "with room to override where local prices differ". Shortfall: only price and availability are named as overridable; Petpooja documents no per-field override rule set, no lock on name/image/recipe, and no statement that a locked corporate field is greyed out or rejected at store level. The multi-outlet guide treats this as an operating policy the owner must decide ("Decide what stays local... work out what head office owns and what an outlet may change"), not as a configurable permission. https://blog.petpooja.com/industry-business-guides/pos-features-for-menu-management/ · retrieved 2026-08-06

multi-location-price-zones

Distinct menus and prices per dine-in area and per aggregator platform. Location-group price tiers on a single item record are not documented. https://petpooja.com/poss/restaurant-menu-management-software · retrieved 2026-08-01

multi-location-scheduled-publish differentiator

Checked the two first-party menu guides on blog.petpooja.com (pos-features-for-menu-management, restaurant-menu-management-software-guide), the multi-outlet menu push guide, and www.petpooja.com/poss/restaurant-menu-management-software. What is documented is recurring time-based menus ("the item appears and disappears on schedule" for breakfast/happy-hour windows) and a head-office push that is triggered when the operator clicks it; the vendor's own worked example of a Diwali card is "prepare the new card in advance and push it to every outlet on the morning of the festival, in one action", i.e. a manual same-day push rather than a future-dated activation. No page states that a push can be dated forward, that activation is interpreted in each outlet's local timezone, or that an activated push can be rolled back - the push log is described only as a status/history screen. Unresolved because the vendor publishes no admin documentation for the head-office push dialog itself (support./help./kb.petpooja.com do not exist).

multi-location-new-store-template differentiator

Checked blog.petpooja.com/industry-business-guides/run-multiple-outlets-one-pos-local-system ("When a new outlet comes on, the Petpooja team maps it to your setup and connects it"), the POS Local hardware/setup guide (a 4-step install performed by Petpooja staff), the POS-types comparison (items and history carry across when you change POS TYPE, which is not the same as cloning an outlet), and the large-chain vertical page. None describes cloning a source outlet's menu, taxes, roles, printers, modifiers or tenders into a new one, and none publishes an expected time-to-open; the vendor's only speed statement is in a payroll article ("live in minutes") about attendance devices, not POS configuration. Note that outlet-to-outlet item copy IS attributed in Petpooja's own comparison article to a competitor (eZee), not to Petpooja. Unresolved because outlet provisioning is a Petpooja-performed onboarding service with no published runbook.

multi-location-corp-vs-franchisee-roles differentiator

"The franchisor's HR head needs to see attendance, salary processing status, and compliance deadlines for every outlet from a single login. But the Jaipur franchisee should only see Jaipur's data. Petpooja Payroll is built around this exact model: a head-office view of all branches with role-based access at the franchise level." The article also models COCO/FOCO/FOFO employer split. On the POS side the large-chain page offers a head-office dashboard over all outlets plus "outlet-wise staff rights". Shortfall: the franchisor/franchisee split is documented in the separate Petpooja Payroll product, not in the POS permission model; the POS side is outlet-scoped user rights inside one account, and nothing states that a franchisee is a distinct tenant owning its own banking/settlement and labour data while corporate enforces config. Grade C throughout - vendor blog and vertical pages, no admin guide. https://blog.petpooja.com/people-payroll/franchise-payroll-businesses-india/ · retrieved 2026-08-06

multi-location-royalty-calculation differentiator

Checked www.petpooja.com/poss/large-chain-restaurant-pos-software, which enumerates the head-office module as centralised menu management, centralised monitoring with outlet zones, ERP integration/data lake, central kitchen and multi-outlet reporting - no royalty, ad-fund or franchise-fee line. Also searched blog.petpooja.com via its WordPress search API for "royalty" and "franchisee": the hits are franchise-investment and conclave articles (expansion checklists, investor guides), none describing a Petpooja royalty engine, and the franchise payroll guide covers wages rather than franchise fees. Unresolved rather than absent: a vertical overview page is not an exhaustive module enumeration, and Petpooja publishes no head-office admin documentation.

multi-location-royalty-collection

Checked the large-chain head-office page, the pricing page (which bills the operator per outlet and lists no franchisee-billing service), the marketplace add-on catalogue at /poss/restaurant-app-marketplace (11 first-party services: wireless calling device, kiosk, scan-and-order, purchase manager, digital display, captain app, KDS, token management, table reservation, website, loyalty wallet, SMS, feedback, reconciliation, dynamic reports - none financial-collection), and blog searches for "royalty" and "franchisee". Petpooja Pay+ is described only as a payment/reconciliation layer for guest payments, not for inter-company collection. Nothing states that fees are debited from franchisee accounts or that a franchisee-visible statement exists. Unresolved: an add-on directory is not an exhaustive enumeration.

multi-location-consolidated-reporting

Head-office module aggregates data from all outlets on a single dashboard with city and zone groupings, including inventory consumption and procurement expense. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

Checked the large-chain page ("Download outlet-wise reports on sales, inventory, online orders, staff performance" - outlet-wise, not consolidated by item), the multi-outlet menu guide, and the POS Local dashboard report list (Day End Summary, Item Report, Order Master, Executive Sales - drawn from one shared database but not described as normalising renamed items). The Online Ordering API blueprint at jsapi.apiary.io/apis/onlineorderingapisv210.apib exposes item ids only inside a single restID's menu payload, so it gives no evidence of a cross-outlet corporate item key. The vendor's own multi-outlet guide describes local renaming as menu DRIFT that breaks the item master rather than as something reporting normalises. Unresolved: no reporting schema or head-office admin doc is published.

multi-location-cross-location-giftcard

Liability reporting is documented: "Read the Gift Card Transaction Report in week one. It gives a running summary of every balance issued and redeemed", and "outstanding balances carry into year-end reports as a liability until they expire". Cross-outlet redemption is explicitly NOT guaranteed - FAQ 4, "Can a gift card be used across all outlets of a chain? This depends on how your outlets are set up, so confirm it with your account manager... If you want one balance that travels across several counters, a virtual wallet is built for that." Further shortfalls: gift cards are listed as available on Electron POS only, and no inter-store settlement or redemption reconciliation between separate owners is described anywhere. https://blog.petpooja.com/growth-scaling/restaurant-gift-cards-how-to-run-programme-from-pos/ · retrieved 2026-08-06

multi-location-cross-location-loyalty

"Card top-up and a Virtual Wallet let a diner or employee load a balance once and spend it at any counter... Every order at any counter deducts from that balance", with all counters running under one account and a wallet/credit report available centrally; the loyalty add-on page adds "Monitor all your customer wallets and their points on a single dashboard", and the CRM page says customer data from online, captain, website and in-house orders lands in "one data pool". Shortfall: the shared balance is documented for counters inside a single food-court/canteen account, not for separate outlets of a chain - Petpooja's gift-card guide says whether one balance works across all outlets "depends on how your outlets are set up, so confirm it with your account manager". Order history and profile sharing across outlets is not stated, and Petpooja Loyalty is listed as unavailable on the POS Local build. https://blog.petpooja.com/industry-business-guides/food-court-canteen-pos-multi-counter-billing/ · retrieved 2026-08-06

multi-location-multi-brand differentiator

"Virtual Brand Management - Smoothly manage multiple cloud kitchen brands within the same setup segregated by different tabs. Handle all orders for all brands across aggregators on one POS software, at no extra charge." The POS-types guide lists "brand grouping" as an Electron POS capability for a cloud kitchen running several brands, and the kiosk page describes food-court multi-brand routing so "one brand's order never lands in another brand's KOT printer". Shortfall: the evidence is vertical marketing copy (grade D), and it covers brand segregation of incoming aggregator orders and kitchen routing only - no documentation of separate per-brand menus in the dine-in biller, per-brand receipt/branding, per-brand revenue reporting, or shared-drawer handling. A differentiator yes would need grade A/B, and Petpooja publishes no admin guide. https://www.petpooja.com/poss/cloud-kitchen-pos-software · retrieved 2026-08-06

multi-location-multi-tax-jurisdiction

Taxes configurable per service type, dine-in area and 'regional norms', with GST handling. Per-location exemptions and inclusive/exclusive rules across jurisdictions are not documented. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-01

multi-location-config-audit-log differentiator

The push log is "a screen showing the outlets a change affected, the parts of the menu that went out, how far each one got, and a record of every push", which the vendor says to "read as an audit trail" and which settles disputes with a franchise partner about a price they claim never arrived. Separately, POS Local "records every change made to an order after it is placed, from an edited amount to a removed item or a deleted bill, across all your outlets", paired with User Management so "activity ties back to a named account". Shortfall: the order-edit log is transactional, not configuration; the menu push log records what went where but no page states it records WHICH USER pushed, and it covers menu/price pushes only - not tax, permission or discount objects. No immutability guarantee and no export/query interface is documented. https://blog.petpooja.com/industry-business-guides/multi-outlet-menu-management-update-every-outlet/ · retrieved 2026-08-06

multi-location-enterprise-api differentiator

Large-chain page: "Push all your sales, inventory and customer data directly to your ERP management software. Get access to a data lake enabling integration with any ERP like Dynamic NAV, Tally, SAP, etc." - a cross-outlet export offer, but with no published spec, schema or endpoint. The one API Petpooja does publish, the Online Ordering v2.1.0 blueprint (raw source at jsapi.apiary.io/apis/onlineorderingapisv210.apib, rendered at onlineorderingapisv210.docs.apiary.io), is the opposite shape: 10 endpoints (Push Menu, Fetch Menu, Save Order, order callback, order status, rider webhook, item stock on/off, get/update store status), every one scoped to a single "restID (required) - Unique restaurant mapping id" with app_key/app_secret/access_token issued per mapped restaurant. It returns no transaction-level sales data and has no account-level or multi-outlet authentication. So: cross-location data movement is claimed at marketing level, and the documented API is per-location-credentialed and order-oriented. https://www.petpooja.com/poss/large-chain-restaurant-pos-software · retrieved 2026-08-06

multi-location-central-labor-policy

"When you open a new branch in Karnataka after running five outlets in Gujarat, the system should let you configure Karnataka's minimum wages, PT slab, and overtime rules in one setup... One-time configuration, applied from the first payroll run", plus "Shift scheduling that respects local labour law" for split shifts, overtime caps and weekly-off calculations that "differ by state under the local Shops & Establishments Act", and statutory deductions computed on the employee's work state. Shortfall: this is the separate Petpooja Payroll product, not the POS; attendance is captured on Petpooja's face-scanner/biometric device and rules are applied when payroll is processed. Nothing documents enforcement at the terminal - no blocked clock-in, no break-violation prompt, no predictive-scheduling notice at the POS - so the claim's "enforced at the terminal, not just reported after the fact" half is unmet. https://blog.petpooja.com/people-payroll/franchise-payroll-businesses-india/ · retrieved 2026-08-06

hardware-commodity-devices differentiator

Petpooja sells no proprietary terminal and its own setup guide describes operator-owned commodity kit, but it is specific and demanding: "You need 1 dedicated computer with an Intel i5 or i7 processor, an SSD, and a UPS", "1 TB SSD (an SSD is required; a regular hard disk is not supported for production use)", "A desktop CPU is preferred over a laptop". Shortfall: the POS Local deployment needs a dedicated spec'd desktop rather than any device on hand, Petpooja GO ships on a vendor-supplied Paytm device, and no first-party compatibility list exists. Evidence is a vendor blog post, not product documentation. https://blog.petpooja.com/industry-business-guides/petpooja-pos-local-hardware-setup-guide/ · retrieved 2026-08-02 adversarially verified

hardware-os-platforms

Windows and Android are named for POS and KDS; Captain app is Android. Minimum OS versions and device specifications are not published. https://petpooja.com/poss/kitchen-display-system · retrieved 2026-08-01

hardware-handheld-purpose-built

Vendor documents the alternative: the Captain app is 'configured to work on any android phone'. No purpose-built handheld with drop/IP ratings is offered. https://petpooja.com/poss/captain-ordering-app · retrieved 2026-08-01

hardware-handheld-battery-swap differentiator

The Captain Ordering App is "Configured to work on any android phone", and its FAQ: "You can run the captain app on multiple android-based tabs and mobile phones!" The wireless-calling-device page repeats that captain alerts arrive on "any Android tablet your captains already use", and the POS-types comparison lists the Captain App as software available on Local and Electron builds with no Petpooja-branded handheld SKU. Petpooja's own hardware catalogue on /poss/restaurant-app-marketplace sells a wireless calling device, a kiosk and (under Payroll) a face scanner - no server handheld. With the handheld being customer-supplied consumer Android, Petpooja neither offers a field-replaceable battery nor publishes any shift battery rating; note that it DOES publish a battery figure for the one handheld device it does sell, the wireless calling device ("15 to 20 days"), which shows the absence here is not merely an unpublished spec. https://www.petpooja.com/poss/captain-ordering-app · retrieved 2026-08-06

hardware-handheld-lte

Checked www.petpooja.com/poss/captain-ordering-app ("Supports offline architecture, works without internet"; FAQ: the app "perfectly syncs with the POS itself" in offline mode), the POS-types comparison (5-day offline billing on Android POS, Local and Electron; none on Lite), and the POS Local hardware guide, where captain devices reach the Bridge Server over the outlet LAN on port 7000 - a path a cellular link would not serve. The captain handheld is any Android phone or tablet the restaurant already owns, so a SIM may be present, but Petpooja nowhere documents cellular as a supported failover, provisions connectivity, or describes a vendor-supplied failover router. Unresolved: what the vendor documents is a different mitigation (local/offline operation) for the same failure, which is not the capability as worded.

hardware-offline-mode

Offline billing since 2017 plus a 'Local POSS' SKU storing data on the local device. No published matrix of which functions degrade offline. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-01

hardware-kds

Petpooja's own pricing page lists "Kitchen display system" in the Add-ons block, not the included-features block (Cloud Billing, 80+ Reports, in-built CRM, unlimited terminals/user rights, central kitchen module, multi-terminal billing, on-call/on-chat support). It is a first-party but separately-purchased module at unpublished price. A flat "yes" reads as bundled KDS. https://petpooja.com/poss/pricing · retrieved 2026-08-01 adversarially verified

hardware-kiosk differentiator

Wall-mount and floor-mount kiosks at 22/27/32 inches with built-in thermal printer and UPI/card payment, via Addsoft and Posbank. No ADA documentation. https://petpooja.com/poss/self-service-kiosk · retrieved 2026-08-01

hardware-drive-thru

Enumerated www.petpooja.com/sitemap.xml: the ten outlet verticals are fine dine, QSR, cafe, food court, cloud kitchen, ice cream, bakery, bar and brewery, pizzeria and large chain - no drive-thru vertical. The first-party device pages (self-service kiosk, wireless calling device, digital display system, token management, KDS) describe indoor floor and counter hardware; the Digital Display System is pitched as turning "the TVs in your outlet into digital menu boards", with no outdoor/weatherised or confirmation-display variant. A WordPress search of blog.petpooja.com for "drive through" returned only unrelated articles. Unresolved rather than absent: an outlet-type page set and an add-on directory are not exhaustive hardware enumerations, and drive-thru is a rare format in Petpooja's India/Gulf market so silence is weak evidence.

hardware-printer-compatibility

Per-station printer assignment on commodity hardware implies standard thermal printers. No published multi-manufacturer compatibility list. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-01

hardware-peripherals

Cash-drawer reporting, thermal printers, wireless calling device and digital display system are supported. Scales, barcode scanners and a published compatibility matrix are not documented. https://petpooja.com/poss/restaurant-app-marketplace · retrieved 2026-08-01

hardware-p2pe-terminal

Checked www.petpooja.com/security (a vulnerability-disclosure programme with scope and safe-harbour terms - no PCI DSS, PTS or P2PE statement), the pricing page, the marketplace catalogue, and blog.petpooja.com/finance-compliance/card-vs-upi-why-restaurant-payment-reports-never-match, which describes Petpooja Pay+ as "the payment layer inside POSS" that splits card/UPI/wallet/cash tenders and reconciles them against "what the provider actually paid" for "connected terminals and UPI partners" - i.e. Petpooja integrates acquirer-supplied terminals rather than certifying its own. The captain app page mentions single-tap card payments under INR 5000, again over a third-party rail. No page names a PCI-listed PTS device, a validated P2PE solution, or the merchant's SAQ type. Unresolved: Indian acquirer terminals do keep card entry off the POS in practice, but Petpooja makes no scope statement I can cite.

hardware-tap-to-phone differentiator

'Single tap contactless card payments under INR 5000' on the Android Captain device, plus UPI and wallets, with no separate reader described. https://petpooja.com/poss/captain-ordering-app · retrieved 2026-08-01

hardware-pricing-transparency differentiator

No hardware SKU prices are published anywhere; the kiosk page routes to a demo booking for pricing. https://petpooja.com/poss/self-service-kiosk · retrieved 2026-08-01

hardware-ownership-vs-lease differentiator

"Is the hardware a one-time cost? Yes, in the main. The computer is a one-time purchase that you own. A cloud plan, by contrast, is a recurring fee for as long as you use it... For most owners, the machine is the main upfront cost, with the software billed as a yearly fee." The billing hardware is merchant-supplied throughout - the POS-types comparison runs the four builds on "any Android phone", "any Android device (7-inch or larger) or all-in-one terminal", and "laptop, desktop or billing terminal" - and www.petpooja.com/poss/pricing quotes software only, per outlet, with no lease or hardware-rental line. Shortfall: this covers hardware the merchant buys for itself. For the hardware Petpooja actually supplies (self-service kiosk, wireless calling device, Payroll face scanner) no page states purchase versus rental terms or a price; the kiosk page only implies purchase via a "4 mo hardware payback" figure, and the payroll bundle advertises "software, hardware, setup all included" in a per-outlet subscription, which points the other way. https://blog.petpooja.com/industry-business-guides/petpooja-pos-local-hardware-setup-guide/ · retrieved 2026-08-06

hardware-usable-after-churn differentiator

Read www.petpooja.com/terms-and-conditions and /cancellation-and-refund-policy end to end: both address subscription fees, refunds, termination and a 2-day post-termination data-download window, with no clause about hardware, device deactivation or return. The POS Local setup guide says the merchant buys and owns the server PC and the POS-types page shows all four builds running on commodity Android/Windows/Mac devices the merchant supplies, which makes software-locking implausible for billing hardware - but that is inference, not a vendor statement, and it does not cover the devices Petpooja does sell (kiosk, wireless calling device, Payroll face scanner), each of which pairs to a Petpooja account. Unresolved: no first-party statement either way exists to cite.

hardware-rma-sla differentiator

"Petpooja Payroll ships its own face-scanner device with a lifetime warranty, so whether the branch is in Vastrapur or Madhapur, every outlet captures attendance the same way." That is a published warranty term. Shortfall: it covers the attendance device in the separate Payroll product only; no warranty term is published for the self-service kiosk, the wireless calling device or any billing hardware, and no replacement or advance-exchange SLA with a stated turnaround (depot swap, next-business-day, on-site window) appears on any page - /poss/support advertises 24x7 multilingual phone and chat support with a named point of contact per outlet, which is a software support commitment, not a hardware RMA. The terms and cancellation pages contain no hardware clauses at all. https://blog.petpooja.com/people-payroll/franchise-payroll-businesses-india/ · retrieved 2026-08-06

hardware-byod

Captain app runs on any Android phone, making staff BYOD practical. A documented permission and security model for personal devices is absent. https://petpooja.com/poss/captain-ordering-app · retrieved 2026-08-01

hardware-remote-device-management differentiator

Checked the POS Local hardware/setup guide and the multi-outlet POS Local guide (the Local Dashboard is described as carrying four sales reports - Day End Summary, Item Report, Order Master, Executive Sales - not device health; installs, static IP changes and outlet mapping are performed by the Petpooja team), the POS-types comparison, the KDS/token/kiosk device pages (the kiosk page promises "continuous software updates" but describes no rollout control), and the marketplace add-on catalogue. The only device-status surface found anywhere is on www.petpooja.com/payroll - "Easily track the status of your biometric device" - which is the attendance device in a different product. Nothing documents an online/offline view of terminals, printers and KDS, remote reboot, per-device software-version visibility, or staged/ringed update rollout. Unresolved: Petpooja publishes no operations or admin console documentation.

hardware-selfpour-scales

Read blog.petpooja.com/industry-business-guides/bar-brewery-pos-india-liquor-pilferage-control in full alongside www.petpooja.com/poss/bar-and-brewery-pos-software. The documented mechanism is manual: "Set each drink as a recipe with its measure, such as a 30 ml or 60 ml peg. Stock deducts that measure the moment the drink is billed. A daily stock closing check compares expected stock against what is actually left." Its own bar-POS capability table (recipe-based deduction, consumption/variance tracking, pilferage controls, user rights, multi-terminal, happy-hour pricing, tabs and splits, state excise reports) contains no metered-pour row, and neither the marketplace add-on catalogue nor the integrations page lists a tap-wall, flow-meter or pour-spout partner. Unresolved: neither list claims to be an exhaustive integration enumeration, and Petpooja advertises 150+ third-party integrations it does not publish.

hardware-callerid-integration

"When the agent enters the number, the screen shows that customer's past orders and saved address. A regular does not have to spell out their lane again", and the order the agent builds drops into the chosen outlet's POS queue and prints a KOT. Shortfall: there is no telephony integration and no caller-ID hardware - the lookup is triggered by a manually keyed phone number, and the vendor is explicit that "Nothing about the call itself is recorded here. Call length and recordings belong to your phone system, not to the ordering screen." So the customer record surfaces on the order screen but nothing pops on an incoming call, and the module runs on Electron, Local and Android POS but not on POS Lite. https://blog.petpooja.com/industry-business-guides/restaurant-call-centre-software-phone-orders/ · retrieved 2026-08-06

extensibility-public-api-docs

Verified myself. https://petpooja.com/poss/restaurant-integrations contains no endpoints, no auth model, no schemas and no developer-portal link — only "Connect with us to integrate your service with Petpooja POS" and repeated "Take a free demo" CTAs. It does not even name specific integration partners on-page. This is the strongest-supported negative in the dossier. https://petpooja.com/poss/restaurant-integrations · retrieved 2026-08-01 adversarially verified

extensibility-api-access-cost differentiator

Enumerated www.petpooja.com/sitemap.xml (46 URLs, no developer or API-pricing page) and read the whole plan comparison on www.petpooja.com/poss/pricing: the Core/Growth/Scale matrix lists Cloud Billing, Inventory Module, 80+ Reports, in-built CRM, Menu management, unlimited terminals and user rights, central kitchen module, multi-terminal billing, the add-on list, Dynamic Reports and support tiers, with no API or integration line item at any tier. Petpooja's own Online Ordering API blueprint (onlineorderingapisv210.docs.apiary.io) says only that credentials for staging and production 'will be provided by petpooja team' and states no fee, and developerapi.petpooja.com returns HTTP 403 to an anonymous request. No first-party statement exists either way, so neither inclusion in the base subscription nor a surcharge can be asserted.

extensibility-partner-revshare

The POSS Reseller Program page publishes the commercial term directly: refer Petpooja POS and 'earn 15% of assured revenue', followed by 'No hidden charges. Straight commission with every conversion.' Registration is gated on document screening. Integration-partner terms, by contrast, are not published - /poss/restaurant-integrations offers only a 'Become our integration partner' contact mailto. https://www.petpooja.com/poss/reseller-program · retrieved 2026-08-06

extensibility-free-sandbox differentiator

The Online Ordering API V2.1.0 blueprint states: 'Access to developer account of staging/production : https://developerapi.petpooja.com/' and 'Credentials for both staging and production environment will be provided by petpooja team.' A staging environment therefore exists and is distinct from production. Shortfall: there is no self-service signup - credentials are issued by hand by the Petpooja team to approved integration partners, developerapi.petpooja.com returns HTTP 403 to an anonymous request, and the blueprint documents no seeded test data or test-restaurant fixtures. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-oauth-partner-apps

Every endpoint in the complete V2.1.0 blueprint authenticates with the same three static shared secrets passed in the JSON request body - app_key ('Unique code which allows you to track and identify application.[32 characters]'), app_secret ('Unique code for transfer secret data.[40 characters]') and access_token ('[40 characters]') - with Fetch Menu instead taking an 'access-token:' request header. The specification contains no OAuth flow, no authorization endpoint, no bearer token, no scope parameter and no per-operator grant or revocation mechanism anywhere across its ten endpoints. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-webhooks-push

Real server push exists: the Order Callback endpoint ('Online order integration partner must implement this endpoint to allow PoS patner to notify about order status updates post successfull order relay') delivers status values '-1 = Cancelled, 1/2/3 = Accepted, 4 = Dispatch, 5 = Food Ready, 10 = Delivered' plus cancel_reason, minimum_prep_time, rider details and an is_modified flag; Push Menu is pushed 'after every change'; and the Rider Information webhook exists expressly to update delivery status 'without continuously polling with check order status'. Shortfall: callbacks fire only for orders the partner itself relayed via /saveorder (keyed on restID plus the partner's own clientorderID) - there is no order-created, paid, voided or refunded event, and no feed at all for POS-originated dine-in or counter orders. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-webhook-reliability differentiator

The Order Callback request body's complete documented attribute list is restID, orderID, status, cancel_reason, minimum_prep_time, minimum_delivery_time, rider_name, rider_phone_number and is_modified - no signature, digest, nonce or timestamp field of any kind, so deliveries are unsigned. The item-stock and store-status callbacks likewise carry only restID and payload fields. Searching the entire blueprint returns no occurrence of HMAC, signature, retry, backoff, redelivery or replay, and no event log or missed-delivery recovery endpoint is defined. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-order-injection-api

Aggregator and QR orders inject as first-class tickets firing to KOT/KDS, implying a working write path - but no public order-injection API is documented for third parties. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

extensibility-menu-write-api differentiator

In the complete ten-endpoint blueprint, menu data moves outbound only. Push Menu: 'We require an endpoint from the integrator on which petpooja will push the menu after every change.' Fetch Menu lets the integrator pull the catalogue. The two stock endpoints are also outbound - 'This API Endpoint has to be provided by integrator. Petpooja will call this endpoint for toggling the item stock status in the menu on integrator platform' - and in any case only flip inStock true/false with an autoTurnOnTime. The only calls that write into the Petpooja POS are /saveorder and /orderstatus (which accepts status -1 Cancelled only). No endpoint creates or updates items, variations, addons or prices in Petpooja. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-data-symmetry differentiator

The published API is asymmetric on its face. Menu is fully readable (Fetch Menu returns restaurant details, categories, items, variations, addongroups, taxes and discounts) but has no write counterpart. Store status has both a read (/get_store_status) and a write (/update_store_status). Orders can be written (/saveorder) but not read back. Customers appear only as an inbound field on saveorder, and there is no employee or inventory object anywhere in the specification. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-published-rate-limits

The blueprint documents request and response bodies, full attribute tables and named error codes (SO_105, SO_106, UOS_105 among others) for all ten endpoints, and defines 200 and 400 responses only. It contains no numeric quota, no requests-per-second or per-minute figure, no 429 response, no throttling description and no rate-limit or retry-after header anywhere in the document. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-doordash-preferred differentiator

Independently verified. The 2026 DPIP cohort is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast and UrbanPiper (roster as of 2026-05-08). Petpooja is absent. The dossier gave no URL for a scored cell; supplying one. https://developer.doordash.com/en-US/docs/marketplace/overview/getting_started/preferred_integrations_new/ · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

Petpooja's documented direct marketplace integrations are Swiggy, Zomato, Dineout, District and EazyDiner. DoorDash, Uber Eats and Grubhub are not documented. https://petpooja.com/poss/online-order-management-software · retrieved 2026-08-01

extensibility-middleware-compatibility

Fetched www.deliverect.com/en/integrations and www.tryotter.com/integrations - neither names Petpooja - and chowlyinc.com/integrations returns 404. On Petpooja's side, www.petpooja.com/poss/restaurant-integrations renders its entire partner list as a single flat image (Partner_lg.webp on the gumlet CDN) with no machine-readable names, so the '150+ integrations' figure cannot be enumerated; the only integration names in that page's markup are Swiggy and Zomato. Petpooja's Online Ordering API blueprint is the aggregator-facing surface but names no middleware partner. Integration directories are near-universally incomplete, so absence from Deliverect's and Otter's lists is not positive evidence of absence; India's aggregation middleware market also runs on UrbanPiper and DotPe rather than the named US platforms.

extensibility-accounting-connectors

Checked www.petpooja.com/poss/restaurant-app-marketplace, whose first-party add-on set (wireless calling device, self-service kiosk, scan-and-order, purchase manager, digital display, captain app, KDS, token management, table reservation manager, business website, loyalty wallet, SMS marketing, customer feedback, online order reconciliation, dynamic reports) includes no accounting or GL application; www.petpooja.com/poss/restaurant-integrations, whose partner list is a flat image with no readable names; and the complete Online Ordering API blueprint, which has no invoice, ledger or journal-entry endpoint. Zoho's own community help portal states there is no native Zoho Books-Petpooja integration and that one would have to be built on the Zoho Books API. No first-party statement about QuickBooks Online or mapped journal entries was located, and an unenumerable partner image cannot support a no.

extensibility-payroll-export

www.petpooja.com/sitemap.xml lists /payroll as a first-party Petpooja product and blog.petpooja.com/people-payroll documents in-product employee setup. The Online Ordering API blueprint contains no labour, timeclock, shift or employee object at all, so there is no documented API path for hours to leave the system. www.petpooja.com/poss/restaurant-integrations renders its partner list as an image with no readable names, so it cannot be enumerated for Gusto, ADP, Paychex or Paylocity. No first-party page names an external payroll provider, but an unenumerable directory cannot support a no.

extensibility-bi-data-warehouse differentiator

The POS Local setup guide documents scheduled raw-data copies the operator controls: 'POS Local keeps your records safe with built-in backups. You can set them to run on a daily, weekly or monthly schedule, and the system keeps the copies for you', with the guidance to 'save the backups to a separate drive, such as a D: or E: drive', and 'Where is my data stored? On the computer running the Bridge Server at your own restaurant, not on an outside server.' Shortfall: the only mechanism is a scheduled local database backup file on the on-premise POS Local deployment - no S3, SFTP, warehouse or Snowflake destination is supported, no transaction-level export format is specified, and no equivalent is documented for the cloud plans. https://blog.petpooja.com/industry-business-guides/petpooja-pos-local-hardware-setup-guide/ · retrieved 2026-08-06

extensibility-app-marketplace

A public marketplace lists apps across Customer Service, Operations, CRM and Analytics - but the catalogue is overwhelmingly Petpooja's own add-ons, not named third-party apps. https://petpooja.com/poss/restaurant-app-marketplace · retrieved 2026-08-01

extensibility-custom-fields-scripting

Enumerated www.petpooja.com/sitemap.xml and read /poss/restaurant-app-marketplace (first-party add-ons only, none an automation or scripting tool), /poss/reports-and-analytics and /poss/restaurant-menu-management-software; none offers operator-defined custom fields or vendor-hosted scripts. The complete Online Ordering API blueprint uses fixed attribute tables per endpoint with no extensible metadata or custom-attribute object. A partner-facing API schema is not evidence about the admin back-office configuration surface, so absence here cannot support a no.

extensibility-headless-embedded

Save Order is exactly this pattern for ordering surfaces: 'Once a new order is placed by the end user, you can push the order to the Petpooja PoS application by calling the below APIs. On arrival, the order will be in Pending State untill the restaurant partner respond (Accept/Reject) on the particular order.' The payload carries the customer, order items with variations and addons, item-level taxes, discounts, packing and delivery charges with dc_tax_percentage/pc_tax_percentage, payment type, min_prep_time and OTP, and Fetch Menu supplies the catalogue to the external UI. Shortfall: the caller computes and passes its own prices, taxes and totals, so the POS is an ingestion target rather than a transaction engine; there is no open-check, line-edit, tender or payment-authorisation API, and every order lands Pending awaiting a staff accept rather than being driven end to end by the third-party UI. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-api-versioning-deprecation

A changelog is published: the blueprint opens with a dated Changelog running from 28-06-2022 ('Added nutrition data to item object in the menu push/fetch API') to 15-10-2025 ('Introduced BOGO, BXGY and Freebie discounts to menu APIs'), and superseded fields are marked inline - the variations object is annotated 'Do not consume this object. This object has been deprecated', and orderID on Update Order Status reads 'Pass it blank, since the object will be deprecated soon.' Shortfall: no deprecation or breaking-change notice policy is stated - there is no notice period, no sunset date on any of the 'will be deprecated soon' fields, and no versioning scheme beyond the document title V2.1.0. https://onlineorderingapisv210.docs.apiary.io/api-description-document · retrieved 2026-08-06

extensibility-data-portability-exit differentiator

Export exists but is severely time-boxed: 'you shall download your data within 2 days of such expiry or termination.' Format is unspecified. https://petpooja.com/terms-and-conditions · retrieved 2026-08-01

reliability-offline-order-entry

The entire evidentiary basis is one unqualified marketing sentence: "Petpooja restaurant billing software works perfectly well, even in offline mode." I re-read the page — there is no scope statement, no duration limit, no sync/conflict description, and no statement of what fails. The dossier itself scores reliability-offline-feature-matrix "no". A single adjective-laden claim with zero documentation should not carry a yes on a decision-flipping cell. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-01 adversarially verified

reliability-offline-card-auth differentiator

www.petpooja.com/poss/restaurant-billing-software advertises 'Works offline, cloud-based software' and its FAQ answers the connectivity question with an offline mode so 'you don't need to worry about a continuous internet connection to take orders and print bills' - order entry and printing only, with no mention of card capture. blog.petpooja.com's POS Local hardware setup guide describes the on-premise Bridge Server and local network but says nothing about payments. Petpooja is not itself the card acquirer in India (card acceptance runs through separately integrated terminals), and no first-party page states whether store-and-forward is or is not available, so this is undetermined rather than absent.

reliability-offline-decline-liability differentiator

Read www.petpooja.com/terms-and-conditions in full - a short add-on purchase agreement covering services bought through an online payment gateway, definitions of Services and Content, IP ownership and warranty disclaimers - and www.petpooja.com/cancellation-and-refund-policy, which covers subscription refunds (a 15-business-day full-refund window, 30 days to credit, prorated refund on termination). Neither is a card-processing agreement, neither mentions offline or store-and-forward transactions, chargeback allocation or offline caps, and no merchant processing agreement appears anywhere in www.petpooja.com/sitemap.xml.

reliability-lan-degraded-multi-terminal differentiator

Multiple billing counters sync to one master station and KOTs route to station printers. Whether shared check state survives an internet outage across terminals is not documented. https://petpooja.com/poss/restaurant-billing-software · retrieved 2026-08-01

reliability-local-transaction-engine differentiator

The only evidence that "Local POSS" stores data on the local device is a third-party software directory's SKU list. Petpooja's own pricing page publishes three tier names (Core/Growth/Scale) and no Local POSS product line at all. The architectural inference (local transaction engine) is the researcher's, not the vendor's. Third-party roundups are not evidence for a yes. https://petpooja.com/poss/pricing · retrieved 2026-08-01 adversarially verified

reliability-offline-kds-printing

Upheld, and if anything generous. There is no KDS-specific offline statement anywhere I could find; the score rests on extending a billing-page sentence to a separately-sold add-on module. Treat as the weakest kind of partial. https://petpooja.com/poss/kitchen-display-system · retrieved 2026-08-01 adversarially verified

reliability-printer-fallback

www.petpooja.com/poss/restaurant-billing-software documents per-station printer routing - 'Assign a unique printer to every station and send KOTs to the respective stations. Smoothly sync them all with the master POS to keep track of all your orders and their running status' - and blog.petpooja.com's POS Local hardware setup guide covers the whole device topology (Master Billing Station, secondary counters, KDS and captain devices on one local network over port 7000). Neither describes what happens when a configured kitchen printer is unreachable, and no reroute-to-backup-printer or staff-alert behaviour appears on www.petpooja.com/poss/kitchen-display-system either. Nothing states the behaviour does not exist, so this is undetermined.

reliability-sync-conflict-handling

blog.petpooja.com's POS Local hardware setup guide gives the multi-device architecture: 'A single device acts as the Master Billing Station and connects to the Bridge Server directly. Your secondary counters, kitchen display and captain devices then connect through that Master Station', all on one local network via a static IP and port 7000, with 'the billing traffic between them stays on site'. It does not state what happens to concurrent edits when that local network partitions - no last-write-wins rule, merge strategy or operator prompt is described - and www.petpooja.com/poss/restaurant-billing-software addresses only offline order entry and printing.

reliability-offline-feature-matrix

Not published. Petpooja markets offline capability broadly but nowhere enumerates which functions are unavailable offline.

reliability-public-status-page

Enumerated the vendor's own published URL index: www.petpooja.com/sitemap.xml lists 46 URLs (home, /poss and its 30 feature and outlet-type pages, /payroll, /invoice, /tasks, /about-us, /careers, /security and the four policy pages) and contains no status or uptime page; www.petpooja.com/status returns 404. The site footer's complete link set (Privacy, Compliance, Terms, Cancellation & Refund, Corporate Information, Escalation Matrix, Security) has no status link either - 'Compliance' points to the trust.petpooja.com Trust Vault, not a status page. status.petpooja.com returns HTTP 500 with no body, status.petpooja.in does not resolve, and the two common hosted options are unclaimed: petpooja.statuspage.io redirects to atlassian.com/software/statuspage and petpooja.instatus.com redirects to instatus.com. https://www.petpooja.com/sitemap.xml · retrieved 2026-08-06

reliability-contractual-uptime-sla differentiator

Verified: the published terms contain no uptime commitment and no service-credit remedy; service is provided "AS IS" with broad liability disclaimers. https://petpooja.com/terms-and-conditions · retrieved 2026-08-01 adversarially verified

reliability-incident-postmortems

There is no public status page (www.petpooja.com/sitemap.xml and the site footer contain none; status.petpooja.com returns HTTP 500), which removes the usual venue for incident history. blog.petpooja.com, the only other first-party publishing surface, carries product and business guides (POS Local hardware setup, payroll setup, chain operations) rather than engineering or incident content, and www.petpooja.com/security is a vulnerability-disclosure policy describing a report/triage/coordinate/fix flow with no public-disclosure or postmortem commitment. A blog with no incident posts is not an exhaustive enumeration, so this stays undetermined.

reliability-247-live-support

Direct internal contradiction in the vendor's own material. The support page says "24-hour free support, even on holidays and weekends", but the pricing page's comparison matrix lists "On-call/On-chat support" as the baseline entitlement and "24/7 Support" plus "Dedicated POC" in the advanced/upper-tier block. The "included not upsold" conclusion is unsupported and probably wrong. https://petpooja.com/poss/pricing · retrieved 2026-08-01 adversarially verified

reliability-onsite-install differentiator

The support page I re-fetched offers only "Get in-person assistance and personalised solution from our POS experts" plus "Staff training & retraining" - it never mentions installation. The setup guide is closer: "The team installs the Bridge Server and POS Local on your computer" and "Before the team arrives, it helps to have the computer and the UPS ready", which implies an engineer visit without ever stating it. Shortfall: on-site go-live is implied by a vendor blog, never documented; no certified dealer network, no coverage map, and no statement whether it is included or chargeable. https://blog.petpooja.com/industry-business-guides/petpooja-pos-local-hardware-setup-guide/ · retrieved 2026-08-02 adversarially verified

reliability-menu-build-service differentiator

The POS Local setup guide describes a vendor-run guided install that explicitly includes menu transfer: 'The Petpooja team installs the software, sets up the database, and connects your outlet, so you are not left configuring anything technical', and 'POS Local is a fresh setup, not an upgrade from a cloud plan. If you are moving over, the team helps you get your menu and outlets across as part of the same process.' www.petpooja.com/poss/support adds free on-call and in-person training and retraining. Shortfall: the documented menu work is migration of an existing Petpooja menu, the operator is expected to have menu items and item-wise ingredients ready, and no first-party page states that Petpooja builds a net-new menu from a restaurant's printed menu as standard onboarding. The source is a vendor blog guide, not the admin manual. https://blog.petpooja.com/industry-business-guides/petpooja-pos-local-hardware-setup-guide/ · retrieved 2026-08-06

reliability-hardware-replacement-sla

blog.petpooja.com's POS Local hardware setup guide makes the ownership model explicit - 'Is the hardware a one-time cost? Yes, in the main. The computer is a one-time purchase that you own' - with Petpooja publishing a recommended spec (Intel i5/i7, 1TB SSD, UPS) rather than selling the machine. www.petpooja.com/poss/support enumerates what support covers (24/7 online support even on holidays, on-ground assistance, automated ticket tracking, free staff training and retraining, an assigned large-chain team, 18+ Indian languages) with no hardware replacement or advance-exchange entry, and www.petpooja.com/cancellation-and-refund-policy covers subscription refunds only. A support features page is not an exhaustive service catalogue, so this stays undetermined.

reliability-backup-restore

Operator-controlled backups are documented for POS Local: 'Once you are running, POS Local keeps your records safe with built-in backups. You can set them to run on a daily, weekly or monthly schedule, and the system keeps the copies for you', with the instruction to 'save the backups to a separate drive, such as a D: or E: drive. Keep them off the C: drive the software runs on ... That keeps your records safe even if the main system is ever reinstalled', and 'Where is my data stored? On the computer running the Bridge Server at your own restaurant.' Shortfall: this covers only the on-premise POS Local deployment, no restore procedure is documented (only the implication that a reinstall can be recovered from), and no RPO or RTO figure is published for POS Local or for the cloud plans. https://blog.petpooja.com/industry-business-guides/petpooja-pos-local-hardware-setup-guide/ · retrieved 2026-08-06

reliability-pci-dss-4-attestation

The site footer's 'Compliance' link goes to trust.petpooja.com, a Scrut Automation Trust Vault - a Next.js app whose bundle references scrut.io and /api/v1/scrutAIOrchestrator, whose only route is /sites/[slug], and which carries meta robots=noindex. The root and five guessed slugs (/sites/petpooja, /sites/prayosha, /sites/home, /sites/main, /sites/default) all render the app's not-found route, and /robots.txt and /sitemap.xml return the same SPA shell, so no attestation, certificate list or document index is publicly retrievable. www.petpooja.com/security is a vulnerability-disclosure policy naming no certifications, www.petpooja.com/privacy-and-policy cites only the IT Act 2000 and GDPR, and no PCI DSS AoC or validated P2PE listing appears anywhere in www.petpooja.com/sitemap.xml.

reliability-mfa-role-based-access

Role-based user-rights management is documented and unlimited user rights ship on every tier. MFA enforcement on back-office or admin logins is not documented. https://petpooja.com/poss/reports-and-analytics · retrieved 2026-08-01

reliability-self-serve-training

Free on-call and in-person training plus a public YouTube channel and blog templates/checklists. A structured LMS and an on-terminal training mode are not documented. https://petpooja.com/poss/support · retrieved 2026-08-01

reliability-failover-terminal-role differentiator

blog.petpooja.com's POS Local hardware setup guide describes the architecture explicitly: the deployment needs '1 dedicated computer at your restaurant to act as the server' running the Bridge Server on a static IP, and 'A single device acts as the Master Billing Station and connects to the Bridge Server directly. Your secondary counters, kitchen display and captain devices then connect through that Master Station.' The only resilience measure named is a UPS 'to keep the machine running through a power cut and protect your data'. No promotion of a secondary counter to master and no standby server is described - but a hardware and network setup guide is not an availability-architecture document, so absence here cannot carry a positive finding of absence.

reliability-cellular-backup

blog.petpooja.com's POS Local hardware setup guide answers 'What network setup does POS Local need?' with the full requirement - all billing devices on the same local network as the Bridge Server, a static IP for the server machine, and network port 7000 - and notes 'The billing traffic between them stays on site, not on the open internet.' No cellular or LTE failover, dual-WAN or modem option appears there or in the hardware spec, which lists only the computer and a UPS. www.petpooja.com/poss/restaurant-billing-software offers offline mode as the connectivity mitigation instead. Nothing states cellular failover is unsupported, so this is undetermined.

commercial-month-to-month-contract differentiator

The only billing term Petpooja actually states in writing is annual: "We will bill your Payment Method for your yearly membership fee at the end of the free trial period unless you uninstall the App prior to the end of the free trial period." I could not confirm a monthly billing toggle on the pricing page — the fetched page shows tier names, a feature matrix and "Contact us for accurate, localized rates", with every tier routed to Book A Demo. Cancel-any-time from the refund policy supports partial, not yes. https://petpooja.com/terms-and-conditions · retrieved 2026-08-01 adversarially verified

commercial-no-early-termination-fee differentiator

No ETF or liquidated damages appear; annual cancellations are refunded 'to the extent of your usage'. The policy never states 'no early termination fee' explicitly. https://petpooja.com/cancellation-and-refund-policy · retrieved 2026-08-01

commercial-autorenew-terms-published

Terms disclose post-trial billing of the yearly fee unless the app is uninstalled first. No renewal term length or required cancellation notice window is stated. https://petpooja.com/terms-and-conditions · retrieved 2026-08-01

commercial-processing-not-bundled differentiator

I fetched the cited page: its only payment sentence is "Integrate Payment gateways with the website" - it names no gateway and says nothing about processor choice, so the grade E on it was also wrong (it is a first-party marketing page). The terms of service likewise never mandate a Petpooja processor, but absence of a mandate is not positive evidence of choice. Shortfall: no first-party page enumerates supported acquirers or gateways, and Petpooja now markets its own bundled Petpooja PAY / Petpooja GO on a Paytm-supplied device. https://petpooja.com/poss/restaurant-website · retrieved 2026-08-02 adversarially verified

commercial-interchange-plus-published differentiator

No processing rates of any structure are published, because Petpooja does not sell merchant acquiring.

commercial-rate-increase-clause differentiator

Read www.petpooja.com/terms-and-conditions end to end (add-on purchases paid through an online payment gateway, definitions of Services and Content, IP ownership, warranty disclaimers) and www.petpooja.com/cancellation-and-refund-policy (subscription fees non-refundable except a 15-business-day full-refund window, 30 days to credit a refund, prorated refund on termination, no refund where termination follows prohibited conduct). Neither contains a pricing, rate-revision or fee-increase clause, and neither is a card-processing agreement - Petpooja sells POS subscriptions rather than acquiring, and no merchant processing agreement appears in www.petpooja.com/sitemap.xml.

commercial-pricing-published

Tier names and a feature matrix are published but no currency figures; the page says local pricing varies by region and routes every tier to 'Book A Demo'. https://petpooja.com/poss/pricing · retrieved 2026-08-01

commercial-module-unbundling differentiator

Add-ons (KDS, kiosk, loyalty, website, feedback, SMS) are marketplace items and Growth bundles 'any 5 marketplace services'. Independent cancellation without repricing the base plan is not documented. https://petpooja.com/poss/restaurant-app-marketplace · retrieved 2026-08-01

commercial-hardware-purchase-outright

Software runs on commodity Windows/Android hardware an operator can buy anywhere, so no lease is imposed - but no vendor hardware prices are published. https://petpooja.com/poss/kitchen-display-system · retrieved 2026-08-01

commercial-hardware-not-locked differentiator

I re-fetched the cited page. It says "Petpooja's KDS works perfectly well with any Windows or Android-based device" and is "Configured to work on any android phone" - a marketing claim, not a compatibility document. Petpooja publishes no hardware compatibility matrix: no named printer (Epson/Star/TVS), cash drawer or scanner model appears on any first-party page, and the vendor's own hardware guide only advises "Ensure the hardware integrates smoothly with your POS system". Shortfall: no documented third-party peripheral support, and the "200+ hardware" figure is unenumerated. https://petpooja.com/poss/kitchen-display-system · retrieved 2026-08-02 adversarially verified

commercial-implementation-fee-published

No implementation, onboarding, menu-build or training fee is published as an amount or as zero; training is described as complimentary on the support page only. https://petpooja.com/poss/pricing · retrieved 2026-08-01

commercial-data-export-self-serve

Customer data downloads free and unlimited, and reports export. Full transaction-line-item export via CSV or API is not documented, and post-termination access lasts 2 days. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

Customer records export freely. Machine-readable export of loyalty point ledgers and wallet/stored-value liability balances is not documented. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

commercial-post-termination-export-window differentiator

Verified verbatim: "Upon expiry or termination of this Service Agreement, you shall download your data within 2 days of such expiry or termination." Correctly quoted and correctly characterised as punitive. https://petpooja.com/terms-and-conditions · retrieved 2026-08-01 adversarially verified

commercial-data-ownership-clause differentiator

Verified verbatim in the terms: "By submitting Your Content you hereby irrevocably grant us a perpetual, irrevocable, nonexclusive, royalty-free, right to use Your Content" and "Petpooja may monetize some of this Content through the use of third party affiliate programs." Quoted accurately. https://petpooja.com/terms-and-conditions · retrieved 2026-08-01 adversarially verified

commercial-source-available-selfhost

Proprietary SaaS under a standard subscription licence; no source availability or self-hosting (the 'Local POSS' SKU is local data storage, not self-hosted source). https://petpooja.com/terms-and-conditions · retrieved 2026-08-01

commercial-pci-p2pe-tokenization

www.petpooja.com/security covers only vulnerability disclosure, safe harbour and program scope (in scope: production web applications under *.petpooja.com, production APIs, official Petpooja mobile applications, Electron POS) and names no P2PE validation, tokenization design or merchant SAQ type. www.petpooja.com/privacy-and-policy cites the IT Act 2000 and GDPR with no cardholder-data section. The trust.petpooja.com Scrut Trust Vault is noindex and its root and guessed /sites/<slug> routes all render the not-found page, so nothing is readable there. The Online Ordering API blueprint carries only a payment_type label on orders and no card, token or PAN field. No first-party statement exists either way.

commercial-pci-dss-4-controls

Checked www.petpooja.com/security (vulnerability disclosure only - report/triage/coordinate/fix, safe harbour, in-scope and out-of-scope asset lists, no control statements), www.petpooja.com/privacy-and-policy (IT Act 2000 and GDPR framing, no cardholder data environment section), and the trust.petpooja.com Scrut Trust Vault, whose root, /robots.txt, /sitemap.xml and five guessed /sites/<slug> routes all return the Next.js not-found route behind meta robots=noindex. Nothing about MFA for access to a cardholder data environment, back-office login controls, or payment-page script integrity monitoring under Req 6.4.3/11.6.1 is publicly retrievable.

commercial-soc2-attestation

The footer 'Compliance' link resolves to trust.petpooja.com, a Scrut Automation Trust Vault (its bundle references scrut.io and /api/v1/scrutAIOrchestrator, its only route is /sites/[slug], and it carries meta robots=noindex). The root, /robots.txt, /sitemap.xml and five guessed slugs all render the not-found route, and the API base is not exposed in the client chunks, so no certification list or NDA-gated report offer could be read. On the reachable surface, www.petpooja.com/security is a vulnerability-disclosure policy naming no certifications, and www.petpooja.com/privacy-and-policy references only the IT Act 2000 and GDPR. The existence of a trust portal suggests attestations exist, but nothing publicly states SOC 2 Type II or ISO 27001, so this is undetermined rather than absent.

commercial-privacy-dsar-tooling

Free customer-data download and the ability to block a customer from promotional messaging. Locate/export/delete DSAR tooling and an executable DPA are not documented. https://petpooja.com/poss/restaurant-customer-management-software · retrieved 2026-08-01

commercial-wcag-kiosk-accessibility differentiator

www.petpooja.com/sitemap.xml (46 URLs) contains no accessibility, VPAT or ACR page, and the footer's legal link set (Privacy, Compliance, Terms, Cancellation & Refund, Corporate Information, Escalation Matrix, Security) has no accessibility statement. www.petpooja.com/poss/self-service-kiosk describes 'a touchscreen & voice recognition interface to allow your guests to order digitally without walking to the counter', and /poss/scan-and-order and /poss/restaurant-website describe the consumer ordering surfaces - none references WCAG 2.1 AA, Section 508, a VPAT, or a tactile or audio non-visual access mode. Voice recognition as an input method is not a documented non-visual access mode, and its presence is not evidence about conformance reporting either way.

commercial-dual-pricing-compliant differentiator

The Online Ordering API blueprint enumerates the charge model Petpooja carries on an order - service charge (sc_applicable_on, sc_type, sc_calculate_on, sc_value, tax_on_sc), packaging charge (packaging_applicable_on, packaging_charge, packaging_charge_type, pc_taxes_id, pc_tax_percentage), delivery charge with dc_taxes_id and dc_tax_percentage, item-level taxes with gst_type and tax_inclusive, and discounts including BOGO, BXGY and freebie - with no card-type, surcharge, cash-discount or debit-exclusion field anywhere, and payment_type carried only as a label. www.petpooja.com/poss/restaurant-billing-software and /poss/pricing describe GST-structured billing with no surcharge feature, and no receipt or menu-board fee-disclosure requirement is mentioned. This is an aggregator-facing order schema rather than the POS tender configuration, so it cannot by itself establish that the POS lacks a compliant dual-pricing mode.