The NegoBill Assistant: Claude and ChatGPT connected to a shop

Platforms: the web app, Android, iOS · Plans: Included in every plan from Starter; the tools follow the plan (purchases, statements, receipts and low stock from Plus; presets from Business) · Permissions: AI assistant group to connect; every tool re-checks the person's own permissions on each call

Connect

1. NegoBill web → Menu → Business → NegoBill Assistant, open on every plan. The page lists the tools open to this login and shows the ones a higher plan opens with a lock and the plan name. The address shown is https://mcp.negobill.com/mcp.
2. Claude: Settings → Connectors → Add custom connector → the address → Connect. ChatGPT: the NegoBill plugin from the directory once listed, or Settings → Plugins → Create app (Developer mode) with the address and OAuth.
3. The NegoBill sign-in page opens: email or phone and password (no code is asked), choose the store, Allow. The AI app never sees the password. Connections are listed on the same NegoBill Assistant page with Switch off.

Tools

Reads (no confirmation needed): business_info · day_report (one day: sales, GST, collected, due, money in by method, expenses, supplier payments, purchases, new contacts, top items; cost and profit only for those who may see cost) · find_products · find_products_by_barcodes (a list of barcodes, up to 500, in one call) · find_products_by_names (a list of names → EXACT, SIMILAR with candidates, or NONE — the check before a purchase or an add) · get_product · low_stock · find_contacts · contact_summary · contact_statement · sales_summary · list_sales · find_sale (a sale from memory: customer name or phone, a word of an item, the rough amount, days, how it was paid, part of the number, a note — every piece must match) · get_sale · list_receipts · list_purchases · share_sale. Writes (the assistant shows what will be recorded and waits for a yes): create_sale (with its payment) · create_quotation · create_purchase (a supplier’s bill: lines by product id, barcode or exact name, unit cost, batch, expiry, printed prices, extra charges; the supplier by id, phone or name, created if unknown; stock in, amount payable) · record_payment · add_contact · add_product · update_product · add_stock. Bulk writes (one call, up to 500 rows, a verdict per row — used whenever two or more items are added or changed, never a loop of single calls): add_products · add_contacts · add_stock_bulk · update_products (up to 200 rows: sale price, MRP, wholesale price, GST, HSN, barcode, product code, fits, unit) · reprice_purchase (every product on a supplier bill: sale price = buying cost on that bill + a margin percent, rounded up to whole rupees, ₹5 or ₹10; MRP raised only where it was below; the bill itself does not change). A connection that still loops is paced at 120 tool calls a minute and told which bulk tool to use. Suggestions: suggest_capability — when a person asks for something no tool does, the assistant says so, names the nearest way in the app, and files what was asked and what a tool would need to do (the scenario only, never a customer’s name, phone or amount; phones and emails are scrubbed on the server). NegoBill reviews these by how many shops asked; voids, refunds, deletes, settings, staff and plans are kept in the app on purpose and are marked so at once. What is listed follows the plan and the person. On Starter: sales, products, stock, contacts, the day report and payments on sales. From Plus: purchases and supplier bills (create_purchase, list_purchases, reprice_purchase), the contact ledger statement (contact_statement), the receipts list (list_receipts) and low stock (low_stock). From Business: presets (find_presets). A tool outside the plan or the person’s permissions is simply not listed; business_info tells the AI what is closed and which plan opens it. Every tool carries readOnly / destructive / openWorld hints and an output schema; money comes back as “₹1,250.00”, dates as YYYY-MM-DD in the store’s timezone.

Forms in the chat: sale_form, product_form and contact_form — for every sale, and for one product, customer or supplier said in conversation, the assistant opens NegoBill’s own Add-a-product form inside the chat (Claude, ChatGPT, VS Code and other apps that show pages), prefilled with what was said — so the person sees the name and the number the assistant heard before anything is saved. A sale is never made from the chat without its preview: the date, the customer, every line with quantity and price, the total, and only the store’s switched-on payment methods (or Pay later) to choose from; ✓ Create sale in the preview is what makes the bill. The form checks the name, barcode or phone against what the shop already has, shows the match, and only the ✓ Add click creates the record — through the same connection, permission and pacing as every other call. The page holds no token and never talks to NegoBill directly. An app that cannot show pages gets the details as text and the assistant asks for a yes before create_sale, add_product or add_contact.

Skills

Five skills ride with the connector (Agent Skills over MCP): sell-and-quote, stock-and-purchases, money-and-dues, find-and-report, setup-and-bulk. A skill is a short written workflow — which tools to call in what order, what to check before a write, what to confirm, how to read the result out — and each carries the house rules (rupees, store dates, confirm first, one call for many items, a preset is never a line, file what NegoBill cannot do). ChatGPT imports them into the plugin when it is submitted and shows them as chips on the plugin page; a Claude host that speaks the skills extension loads them live from mcp.negobill.com. Together the five name every tool.

What it cannot do

Void or edit a sale, refund, delete anything, change settings, manage staff, buy plans. Those stay in the app. Cost and profit never leave for a person without Buying price & profit. Plans are never sold inside the AI app.

Rules

• One tool registry behind every door (MCP today, the in-app chat later); each tool wraps the same service the web and phones call.
• Plan limits are on the server: the consent page refuses when the plan has ended or the owner switched the Assistant off; a tool outside the plan or the person’s permissions is not even listed.
• Signing in on the consent page opens no device session, so it never signs a phone or browser out.

How-to guides

• connect claude