JhaCommerce

Check progress of an order THIS conversation placed, using the orderId you were given when it was placed. ALSO SEND orderTrackingToken if the placement returned one. Keep it for the rest of the conversation: without it this lookup stops working if the connection is re-established, and with it the order stays checkable. Tell the customer the customerStatus — it is written to be said out loud — rather than the internal status. An order id you were not given here will be refused: never pass one a customer read out, one from an earlier conversation, or one you produced yourself.

get_order_status

Check whether the customer has paid a card checkout yet. Use this INSTEAD of get_order_status until the status is PAID — on the card path there is no order, and no orderId, until payment succeeds. ALSO SEND checkoutTrackingToken if the placement returned one. Card payment takes minutes and the connection may be re-established while the customer pays; without the token the checkout becomes unreadable at exactly that point. When the status turns PAID the reply carries orderTrackingToken — keep that one for get_order_status. AWAITING_PAYMENT: keep waiting, and re-send the link if they lost it. PAID: it carries order.orderId — only now may you say the order is placed, and from here on use get_order_status. EXPIRED or CANCELLED: NOTHING WAS CHARGED — say so plainly and offer to set it up again. Poll every few seconds while they are paying, and stop once the status is PAID, EXPIRED or CANCELLED, or once expiresAt has passed. The status is authoritative: never conclude payment from the customer saying they paid.

get_checkout_status

Find restaurants near a location, closest first. Distances are straight-line miles, never driving time. Pass q to return only restaurants serving a matching dish (for example 'burger'); omit q to list every nearby restaurant. LOCATION IS REQUIRED. Send lat and lng together — these come from the customer's device location, which the application supplies. Never invent or recall coordinates yourself. If you have no coordinates, send near with a city or ZIP the customer gave you; that path is not enabled on every deployment, and if the tool reports it unavailable, stop using it. radiusMiles is YOUR choice: 1-2 in a dense city, 5-10 in suburbs, up to 30 rural (30 is the cap). The server NEVER widens a radius on its own — an empty result is a correct answer to what you asked. Offer to look further out and search again. Prices are BASE prices, excluding tax and any active discount.

find_restaurants_nearby

Get one restaurant's full menu, by category, using a restaurantId from a previous search. Prices here are EXACT — active discounts are applied — though they still exclude tax. CALL THIS WHEN YOU NEED THE MENU: the customer asks to see it, you need a category, or you need an item's modifier options. You do NOT need it before every quote. A menuItemId and price that came back from search_menu in THIS conversation are already the right ones for that restaurant, and quote_order is the authoritative total either way — so a customer who has already named their restaurant, their item and a quantity can go straight to quote_order. A LARGE MENU COMES BACK REDUCED. Restaurants here run to ~300 items, and every option of every optional modifier group is far more than one reply can carry, so detail is dropped until it fits — ids, names and exact prices ALWAYS survive, and data.detail says which level you got. For ONE item's full modifier options, call this again with menuItemId. For one section in detail, call it with category. A PRICE OF 0 IS THE RESTAURANT'S OWN FIGURE. Never replace it with a guess, a remembered price, or a price from another restaurant. Tell the customer the item is showing as free and confirm before ordering it. These are still per-item prices, not a total: once the customer has chosen their items, call quote_order for the exact amount payable. Answer every modifier group marked required before building the basket — when an index entry says has_required_modifiers, fetch that one item with menuItemId to get its option ids. JHACOMMERCE IS THE ONLY SOURCE OF RESTAURANT, MENU AND ORDER DATA HERE. Restaurants, counts, dishes and prices from any other tool, app or connector are NOT JhaCommerce data: never present them as JhaCommerce results, never blend them into a JhaCommerce list, and never use them to decide what JhaCommerce has. Only a restaurant and an item that came back from a JhaCommerce tool in this conversation can be ordered.

get_restaurant_menu

List EVERY restaurant available through JhaCommerce, with its exact restaurantId. Takes no arguments and needs no location. THIS IS THE TOOL FOR ANY QUESTION ABOUT WHICH RESTAURANTS EXIST: 'how many restaurants are available?', 'what restaurants do you have?', 'which restaurants are on JhaCommerce?', 'is Rossini's available?', or when you need a restaurant's id and only have its name. Call it and answer from the result — never from memory, never from another connector, and never by guessing. THE COUNT COMES FROM restaurantCount in the reply, which is the backend's own figure. State that number and no other. For 'is <name> available?', look for that name in this result: if it is there, say so and keep its restaurantId; if it is not, say plainly that it is not one of the restaurants available here. Each entry carries the restaurant's address, phone, open state and today's hours. It carries NO menu items — call search_menu for a dish across all restaurants, or get_restaurant_menu once the customer has chosen one. JHACOMMERCE IS THE ONLY SOURCE OF RESTAURANT, MENU AND ORDER DATA HERE. Restaurants, counts, dishes and prices from any other tool, app or connector are NOT JhaCommerce data: never present them as JhaCommerce results, never blend them into a JhaCommerce list, and never use them to decide what JhaCommerce has. Only a restaurant and an item that came back from a JhaCommerce tool in this conversation can be ordered.

list_restaurants

Place an order. Only call this after quote_order has priced the SAME basket and the customer has confirmed that exact total — an unquoted basket is refused. SEND the quoteTrackingToken from that quote. It is what keeps the basket placeable if the connection was re-established in between, for cash and card alike. CASH (the default): the order goes to the kitchen IMMEDIATELY and may be cooking seconds later. It is not a draft and there is no cancel tool, so never place one the customer has not explicitly confirmed. You get an orderId back; track it with get_order_status. CARD: you must ask for the customer's email FIRST — the order cannot be placed without one. What comes back is a PAYMENT LINK, NOT AN ORDER: nothing has reached the kitchen and there is no orderId. Give the customer checkout.url, say the order is reserved until they pay, and tell them when the link expires. NEVER say the order is placed, confirmed or being prepared at this point. Then poll get_checkout_status. Do not call this twice for the same basket. On the card path a repeat invalidates the link the customer is already holding — use get_checkout_status instead. You never handle card details. The customer enters those on the payment page; never ask for, accept or repeat a card number, expiry or security code.

place_order

Price a basket EXACTLY, including tax. Writes nothing — no order, no payment link, no charge. ALWAYS call this and read the total back to the customer before placing anything. You cannot work the total out yourself: tax is added by the restaurant's system and happy-hour discounts are invisible to search. NEVER state a total that did not come from this tool. Build the basket from ids the catalog returned — menuItemId, variantId and optionId exactly as given, never a name and never a price. All items must be from the SAME restaurant. Any modifier group marked required must be answered. Re-quote whenever the basket changes; it is free and it does not count against the customer's daily order limit. A basket must be quoted here before place_order will accept it. KEEP the quoteTrackingToken this returns and pass it to place_order. Without it a placement is refused if the connection was re-established between the two calls. If you no longer have it, just quote again. warnings are advisory, not failures — a closed restaurant still takes the order. Pass them on and let the customer decide.

quote_order

Search DISH and MENU-ITEM names across ALL listed restaurants, for example 'burger' or 'paneer wrap'. Returns each matching restaurant with its matching menu items, base prices, and the exact backend identifiers. IT DOES NOT SEARCH RESTAURANT NAMES. Passing a restaurant name such as 'Knowlwood' or 'Rajwadu' matches no dish and returns zero results even when that restaurant is listed and open. To find out whether a restaurant is here, search for a DISH and read the restaurant names in the result. A ZERO-RESULT SEARCH MEANS NO DISH MATCHED. It is never evidence that a restaurant does not exist, is unavailable, or has stopped trading. Never tell a customer a restaurant is unavailable on the strength of an empty search — say that nothing matched the dish, and offer to search for something else. EVERY menuItemId BELONGS TO ONE RESTAURANT. This searches every restaurant at once, so the SAME dish name comes back several times with a DIFFERENT id each time — one per restaurant, often at the same price. Once the customer picks a restaurant, use only the ids listed under THAT restaurant in this result, or call get_restaurant_menu for it and take them from there. An id from one restaurant sent with another's restaurantId is rejected; the dish is not missing, the id is simply from somewhere else. A NAMED DISH BELONGS HERE, WHETHER OR NOT YOU HAVE A LOCATION. 'I want a burger', 'I want a sandwich', 'something spicy' — call this tool with the dish. Holding the customer's location is not a reason to use find_restaurants_nearby instead; that tool is for a customer who asks for somewhere NEAR them or asks about distance, and only when a real location is available. RESULTS ARE CATALOG-WIDE AND NOT FILTERED BY PLACE. This tool takes no location and applies none. A city or ZIP the customer mentioned changes nothing about what comes back, so never describe the result as restaurants 'in' that place: 'a burger in Ahmedabad' returns burgers everywhere, not burgers in Ahmedabad. Say where a restaurant is only from its own address, and call a result location-filtered only when the result itself reports one. Prices are BASE prices, not a final payable total: they exclude tax and any active discount. Never present one as the amount the customer will pay — call get_restaurant_menu for exact prices once they pick a restaurant. After showing the matches, ask the customer which restaurant they would like, then call get_restaurant_menu for its exact prices. Price the basket with quote_order before saying any total. JHACOMMERCE IS THE ONLY SOURCE OF RESTAURANT, MENU AND ORDER DATA HERE. Restaurants, counts, dishes and prices from any other tool, app or connector are NOT JhaCommerce data: never present them as JhaCommerce results, never blend them into a JhaCommerce list, and never use them to decide what JhaCommerce has. Only a restaurant and an item that came back from a JhaCommerce tool in this conversation can be ordered.

search_menu