Documentation

Overview

Trakor is a QR-based traceability + billing platform. Every organisation gets a prepaid credit wallet. Credits are consumed only on chargeable actions (listed below). All data is scoped per organisation with row-level security.

• Traceability: Products → QR codes → Delivery Challans → public trace lookup
• Billing: Sales, Proforma, and Purchase invoices with GST (CGST/SGST/IGST auto-detected)
• Accounts: Payments, Customer & Vendor Ledgers (XLS + PDF export)
• Integrations: REST API + Webhooks for Tally, Busy, Zoho or any custom ERP

Platform Video Tour

A 24-second walkthrough of everything Trakor does — traceability, billing & POS, Sales CRM, WhatsApp/email automation and instant ecommerce websites.

Tip: unmute for background music. Share this video with your team as a quick platform intro.

Role Quickstarts

Jump straight to what you need to do next. Pick your role — each card lists the top actions in order with a direct link into the app.

Setup Guide (Getting Started)

Follow these steps once, in order, to go from a fresh sign-in to printing your first QR label and issuing your first invoice.

1. Sign in. Use the phone + password credentials shared by your Org Admin (or by your Reseller). If you forgot the password, use Reset via OTP on the sign-in page.
2. Complete organisation details. Go to Settings → Organisationand fill in legal name, GSTIN, state, address, and logo. State is critical — invoices auto-pick CGST+SGST when the party is in the same state, IGST otherwise.
3. Invite your team. Settings → Members → add users with role Org_Admin, Manager, Challan_Operator, or Viewer. Share the auto-generated password with each member.
4. Check your wallet. The header shows current credits. If it's low, ask your Reseller to recharge. Every QR code, challan, and invoice consumes 1 credit.
5. Add master data. Create Products, Parties (customers), and Vendors — either one at a time or via XLS import (use the "Download template" button on each list). Set HSN, UoM, GST %, and price-inclusive/exclusive on each product.
6. (Optional) Design a QR label template. Settings → QR Templates → drag product fields, custom fields, images, and the QR placeholder onto the canvas. Mark one as default. Skip this to use the built-in 24-per-A4 label.
   Cost: 10,000 credits per new template.
7. Generate QR codes. QR → Generate → pick a product and quantity. QR codes appear in QR History; select rows → Download QR Codes for a printable A4 PDF.
8. Create your first Delivery Challan. Challans → New → pick a party, then either search products, scan the printed labels full-screen, or type the last 8 characters of a QR ID. Save to generate a challan PDF.
9. Convert to Invoice. Open the saved challan → Convert to Invoice. Tax mode, HSN, UoM, and totals are prefilled. Add E-way / E-invoice details if applicable, save, and download the PDF.
10. Record payments. Open any invoice → Record payment (full or partial). Payment status (Pending / Partial / Paid) updates automatically and reflects on the invoice list and the customer ledger.
11. (Optional) Integrate with your ERP. Settings → API Keys → generate an X-API-KEY, then push products / parties / vendors via the REST API (see below).

Onboarding Checklist

Tick each item as you finish it. Progress is saved in this browser so you can come back later and pick up where you left off.

Onboarding by Role

Pick your role for a first-week checklist. Every step links to the matching docs section and the exact screen in the app. Progress is saved per role in this browser.

Role-Based Instructions

Trakor uses these roles inside your organisation. Each workflow below lists exactly what each role must (or cannot) do.

Full Role Access Matrix

Every role in the platform and exactly what it can do. Roles are assigned per organisation in Settings → Members; Super Admin and Reseller Admin are platform-level roles assigned from the admin console.

Complete Feature Catalog

Module-by-module list of every feature currently shipped, where to find it, and which roles can use it.

WhatsApp & Email Automation

Landing Pages & Lead Webhooks

1. Build a page in CRM → Landing Pages with the drag-and-drop editor and publish it to a public URL.
2. Drop in a lead capture form — submissions land straight in the CRM pipeline at your chosen stage.
3. For third-party sources, create a webhook in CRM → Webhooks; each gets its own intake token at /api/public/v1/lead-intake/<token>.
4. Map incoming query parameters or JSON keys to lead fields; unknown fields can be auto-created as custom fields.
5. Enable HMAC-SHA256 signature verification and the replay guard for trusted senders.
6. Deduplication rules merge repeat leads by phone or email instead of creating duplicates.
7. Slack and email notifications fire on every new lead; conversion analytics are per landing page.

Website Custom Domain Setup

Your storefront is always reachable at /store/<your-slug>. To serve it on your own address (for example shop.yourcompany.com), follow these steps in order.

1. Open Website → Settings.
2. Set the store name and the web address (slug) — lowercase letters, numbers and hyphens only.
3. Turn on Make store live and click Save. A store that is not live returns "store could not be loaded" on any domain.

1. In Website → Settings → Custom domain, type the exact hostname visitors will use, without https:// and without a trailing slash.
2. Use one hostname per store. If you want both example.com and www.example.com to work, add both at your DNS provider and redirect one to the other.
3. Click Save. The domain is stored against your storefront so incoming requests for that host resolve to your store.

• Delete any old A, AAAA or CNAME record for the same host — conflicting records block verification.
• If your DNS is proxied (Cloudflare orange cloud), enable the proxy option during domain setup so CNAME-based verification is used instead of A records.
• SSL is issued automatically after verification. If you use CAA records, allow Let's Encrypt.
• Propagation is usually minutes but can take up to 72 hours. Check with dnschecker.org.

1. Go to Website → Settings and click Visit. It opens your live storefront in a new tab.
2. While the domain is still propagating, Visit uses the /store/<slug> address — confirm the shop, products and cart render there first.
3. Once DNS is live, open your custom domain directly in a fresh tab (or a private window) and confirm the same storefront loads with a padlock (https).
4. Check a product page, add to cart, and open a policy page such as /policy/privacy to confirm deep links work on the custom host.
5. Place one test order — it should appear in Website → Orders and create a matching lead in the CRM.

• "This store could not be loaded" — the store is not live, or the domain saved in settings does not exactly match the host in the browser (watch for www).
• Visit opens a blank tab — the slug was changed after publishing; save again and retry.
• Certificate warning — DNS resolved but SSL is still being issued; wait and reload, then retry issuance if it persists.
• Old site still showing — a stale A/CNAME record or browser cache; clear the cache or test in a private window.

Ecommerce Setup Cheatsheet

Everything needed to take a storefront live, in the order you should do it. All of it lives under Website → Settings.

• The Web address field on the General & design tab is your slug; the public URL is /store/<slug>.
• Slugs are auto-cleaned as you type: lowercase letters, numbers and hyphens only, max 60 characters. Spaces and symbols become hyphens.
• Sub-pages follow the same prefix — /store/<slug>/product/<id>, /store/<slug>/cart, /store/<slug>/policy/privacy.
• Changing the slug changes every public link instantly; old links stop working, so update anything you have already shared.
• A custom domain serves the same storefront at your own address — see Website Custom Domain Setup. The /store/<slug> URL keeps working alongside it.
• The storefront only responds when Make store live is on; otherwise visitors see "this store could not be loaded".

• The storefront footer always links Privacy Policy, Return & Cancellation Policy and Terms & Conditions — you do not add these links manually.
• They point at /store/<slug>/policy/privacy, /policy/returns and /policy/terms and follow your slug or custom domain automatically.
• Left blank, each page publishes a standard version built from your store name and contact details — see Store Policy Pages.
• Razorpay and most gateways require these three pages plus a reachable contact address before approving a live account.
• The footer also shows your contact phone, WhatsApp and email, so fill those in before going live.

• Catalogue — switch on Publish online for every product you want listed; unpublished products stay hidden.
• Shipping — pick flat rate, zones or weight slabs, set free-shipping threshold and pickup instructions.
• Payments — enable Cash on Delivery and/or Razorpay (Key ID plus secret, stored securely and never shown again).
• Policies — review or replace the three policy pages.
• SEO — page title (≤60 chars) and meta description (≤160 chars).
• Finally turn on Make store live, click Save, then Visit and place one test order — it lands in Website → Orders and creates a CRM lead.

Store Policy Pages (Privacy, Returns, Terms)

Every storefront publishes three policy pages that are linked in the website footer and required by payment gateways such as Razorpay. Each organisation gets its own copy.

• If a policy box is empty, the public page automatically renders a standard version — the page is never blank or missing.
• The generated text is personalised with your store name, contact email / phone and address from Website → Settings, so filling those in first produces better copy.
• Auto-generated text is not stored in the database; it is produced at page load, so it updates instantly when you change your store name or contact details.
• The moment you type your own text and save, your version replaces the standard one everywhere.
• Clearing the box again reverts that page back to the auto-generated version.

1. Open Website → Settings and select the Policies tab.
2. Edit any of the three boxes: Privacy Policy, Return & Cancellation Policy, Terms & Conditions.
3. Click Use standard text to drop the auto-generated draft into the box so you can edit it instead of writing from scratch.
4. Click Save. Changes are live immediately — no republish needed.
5. Use Preview next to each box (shown once the store is live) to open the public page in a new tab.

Coupons & Discounts

• Create percentage or flat-amount coupons in Settings → Coupons.
• Set a validity window, minimum order value, total usage cap and per-customer limit.
• Apply coupons at POS checkout and on invoices; every use is written to the redemption log.
• Deactivate a coupon at any time without touching past redemptions.
• Org Admin and Accountant manage coupons; POS and billing users can only apply them.

Super Admin & Reseller Administration

End-to-End Example: QR → Purchase → Invoice → Ledger

A single realistic scenario for Acme Fabrics Pvt Ltd (Karnataka, GSTIN 29ABCDE1234F1Z5), selling to Blue Retail LLP (Karnataka — intra-state, so CGST + SGST) and buying from Yarn Mills Co (Tamil Nadu — inter-state, so IGST). Wallet balance at the start: 10,000 credits.

Role-Tailored Walkthroughs

Five end-to-end walkthroughs, one per workflow, each driven by the role that typically owns it. Sample data uses Acme Fabrics Pvt Ltd (KA) with vendor Yarn Mills Co (TN) and customer Blue Retail LLP (KA).

curl https://dc.innosate.com/api/public/wallet \
  -H "x-api-key: trk_live_..."

curl -X POST https://dc.innosate.com/api/public/products \
  -H "x-api-key: trk_live_..." -H "content-type: application/json" \
  -d '{"sku":"CY-40","name":"Cotton Yarn 40s","gst_percent":5,
       "price":250,"hsn_code":"5205","unit_of_measure":"kg"}'

curl -X POST https://dc.innosate.com/api/public/qr/generate \
  -H "x-api-key: trk_live_..." -H "content-type: application/json" \
  -d '{"sku":"CY-40","quantity":100}'

Credit Pricing

Every chargeable action deducts credits from the organisation wallet. Deduction is atomic — a creation fails cleanly if the wallet is empty. Org Admins can top-up via their reseller.

Feature Guide

Inventory Workflow

Inventory in Trakor is serial-first: each physical unit becomes a QR code that tracks its status (unassigned → in-challan → delivered → in-invoice).

1. Master products. Products → add name, SKU/HSN, UoM, GST %, price, and toggle price includes GST. Add custom fields (batch, colour, warranty, etc.) that flow into labels and PDFs.
2. Purchase intake. Purchases → New → pick vendor, add products and quantities. Saving records the purchase invoice and vendor ledger entry.
3. Generate serial QR codes. QR → Generate → pick a product and quantity to create that many unique QR codes (status: unassigned).
4. Print labels. QR History → filter → select rows → Download QR Codes. Uses your default template or the built-in 24-per-A4 layout.
5. Dispatch. Scan the printed QR on Challans → New. Status flips to in-challan, then to delivered once the challan is saved.
6. Search & audit. Filter QR History by date / status / party, export to XLS, or open Traceability to look up any unit by full ID or last 8 characters.

Tracking & Traceability Workflow

Every QR code carries the product's full history. Use tracking for warranty claims, returns, field service, and dispatch verification.

1. Scan or type. Open Traceability and either use the camera scanner or enter the last 8 characters of the QR ID (case-insensitive).
2. Read the trace card. You'll see product details, custom fields, current status, assigned party (if any), source challan / invoice, and full timeline.
3. Public lookup URL. Every code exposes /t/<qrId>. Access is restricted to authenticated members of the owning organisation.
4. Bulk verification at dispatch. Use the full-screen scanner on Challans → New: valid scans beep + add to cart, already-assigned or unknown codes give an error beep and stay out of the cart.
5. Chat bot lookup. Open the chat, sign in, then ask "trace <last-8-chars>" for a quick text summary — useful on the shop floor.

Billing Workflow

The typical customer-facing document chain is Proforma → Delivery Challan → Sales Invoice → Payment. You can start at any step; convert buttons prefill the next document.

1. Quote (optional). Proforma → New → pick party, add products, save. Series PI-YYYY-######. Download / share PDF with the customer.
2. Dispatch. Challans → New → scan or search QR codes → save. Series DC-YYYY-######. PDF mode (per-unit rows vs grouped quantity) is set in Settings → Organisation.
3. Invoice. Open the challan (or the proforma) → Convert to Invoice. All items, HSN, and totals are prefilled. Tax mode is auto-picked:
   • Same state as your organisation → CGST + SGST split evenly.
   • Different state → IGST at the full rate.
   • Product's price includes GST flag decides whether the rate is added on top or reverse-calculated.
4. Compliance fields. Add E-way Bill number + date and E-invoice IRN / Ack No / Ack Date on the invoice editor. They render on the PDF and export to XLS.
5. Send the PDF. Use per-row Download or Print from the invoice list — no need to open each invoice.
6. Record payments. Full or partial. Status auto-syncs (Pending / Partial / Paid), and the amount flows into the customer ledger.
7. Purchase side. Purchases → New mirrors the sales flow for incoming stock, and posts to the vendor ledger.
8. Period statements. On any party or vendor row click Ledger, pick a date range, and export XLS or A4-landscape PDF for the customer / auditor.

Sales, Proforma & Purchase Invoices

• Sales Invoice (/invoices) — series INV-YYYY-######, issued to a Party. Optional E-way / E-invoice fields.
• Proforma Invoice (/proforma) — series PI-YYYY-######, one-click Convert to Invoice.
• Purchase Invoice (/purchases) — series PUR-YYYY-######, one-click Convert to Proforma or Convert to Invoice.
• Tax mode is derived automatically: same state = CGST+SGST; different state = IGST.
• Each list supports search, party/vendor filter, status filter, payment-status filter, date range, column sort, pagination, per-row Download / Print PDF, and XLS export.

Cost: 1 credit per document (configurable).

Payments & Ledgers

• Record part or full payments on any Sales / Proforma / Purchase invoice from its detail page.
• paid_amount and payment_status (Pending / Partial / Paid) update automatically via DB triggers.
• Invoice list has color-coded Payment Status chips and filter.
• Customer Ledger (Parties → Ledger): date range, opening/closing balance, XLS + PDF.
• Vendor Ledger (Vendors → Ledger): same, sourced from Purchase Invoices.

Delivery Challans & QR Traceability

• Generate unique QR codes per unit. Wallet blocks generation at 0; warns at ≤ 50.
• New Delivery Challan: product search, live camera scanner (full-screen), 8-character QR suffix lookup, cart in local storage.
• Convert Challan → Sales Invoice in one click; invoice links back to source challan.
• PDF mode configurable per organisation: single row per unit OR grouped by product with total quantity.
• Public trace at /t/<qrId>; access restricted to authenticated organisation members.

QR Label Templates

• Drag-and-drop designer with product fields, custom product fields, uploaded images, and QR placeholder. Horizontal + vertical alignment.
• Mark one template as default. If none set, built-in 24-per-A4 layout is used.
• Search, sort, and paginate templates. Duplicate any product for quick variants.
• Cost: 10,000 credits per new template. Organisations below 10,000 credits are blocked with a clear message.

Point of Sale (POS)

POS Setup Guide

POS Workflow Examples

Product Barcodes

Barcode Printing Specs

Troubleshooting: Scanning & Printing

POS Offline Mode & Caching

Sales CRM (Field Force)

Attendance, GPS Tracking & Party Visits

Leads, Pipeline & Configurable Stages

CRM Calendar & Follow-ups

CRM Subscription, Seats & Billing

Organisation, Members & Roles

• Organisations and their first Org Admin are provisioned by your Reseller.
• Org Admin manages members (add/edit/delete + assign role + set password), API keys, and QR templates.
• Roles: Org_Admin, Manager, Challan_Operator, Viewer.
• Managers can generate QR codes and create challans / invoices. Viewers are read-only.
• Frozen organisations can neither generate QR codes nor create documents (API returns 403).

API — Authentication

Generate an API key in Settings → API Keys. Pass it on every request via the X-API-KEY header.

https://<your-app-domain>/api/public/v1

X-API-KEY: sk_live_your_secret_api_key_here
Content-Type: application/json

Keys are scoped to a single organisation. Revoked or invalid keys return 401 Unauthorized. Frozen organisations return 403 Forbidden.

API — Products

Optional q filters by name (ILIKE). limit max 200.

{
  "data": [
    { "id": "9c7a...", "sku": "PRD-00042", "name": "Steel Rod 12mm", "description": null, "price": 450 }
  ]
}

{
  "name": "Steel Rod 12mm",                 // required
  "description": "Construction-grade rebar", // optional
  "price": 450.00                            // optional, default 0
}

Idempotent by name. Existing rows return "created": false.

curl -X POST https://<your-app-domain>/api/public/v1/products \
  -H "X-API-KEY: sk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"name":"Steel Rod 12mm","price":450}'

API — Parties (Customers)

{
  "name": "Acme Distributors Pvt Ltd",   // required
  "contact_info": "Ravi | +91 98765 43210 | ravi@acme.in"  // optional
}

Idempotent by name. GET returns id, name, gstin, state, phone, alt_phone, contact_info.

API — Vendors

{
  "name": "Northline Steel Mills",   // required
  "gstin": "27AAAAA0000A1Z5",        // optional
  "state": "Maharashtra",             // optional
  "phone": "+91 98765 43210",         // optional
  "alt_phone": "+91 22 4000 0000",    // optional
  "email": "sales@northline.example", // optional
  "contact_info": "GST + credit terms 30d" // optional
}

Idempotent by name. Use vendors on Purchase Invoices.

curl -X POST https://<your-app-domain>/api/public/v1/vendors \
  -H "X-API-KEY: sk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"name":"Northline Steel Mills","gstin":"27AAAAA0000A1Z5","state":"Maharashtra"}'

API — CRM Leads (fetch & update)

Read and update CRM leads from any external system. These endpoints use your organisation API key (Settings → API keys) in the X-API-KEY header — different from the intake webhook token, which only creates leads.

Returns { data: [...], count, limit, offset } ordered by last update. updated_sincetakes an ISO timestamp so you can poll for changes only.

curl "https://<your-app-domain>/api/public/v1/leads?stage=Qualified&limit=20" \
  -H "X-API-KEY: sk_live_xxx"

{
  "data": {
    "id": "…",
    "name": "Ravi Sharma",
    "company": "Sharma Industries",
    "phone": "+919876543210",
    "email": "ravi@sharmaind.com",
    "address": "12, MIDC Road", "city": "Pune", "state": "Maharashtra", "pincode": "411026",
    "source": "Google Ads",
    "stage": "Qualified",
    "expected_value": 250000,
    "expected_close_date": "2026-09-15",
    "notes": "Needs 500 QR labels per month",
    "attachments": [{ "name": "Requirement.pdf", "url": "…" }],
    "custom_fields": { "product_interest": "QR labelling" },
    "assigned_to": "…",
    "created_at": "…", "updated_at": "…"
  },
  "activities": [
    { "activity_type": "stage_change", "from_stage": "New", "to_stage": "Qualified", "created_at": "…" }
  ]
}

Send only the fields you want changed (PUT behaves the same). custom_fields is merged with the existing values, so you can update a single additional field. A stage change is recorded in the lead timeline automatically.

curl -X PATCH https://<your-app-domain>/api/public/v1/leads/<lead_id> \
  -H "X-API-KEY: sk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
        "stage": "Negotiation",
        "expected_value": 350000,
        "notes": "Quote revised after site visit",
        "custom_fields": { "product_interest": "QR labelling + POS" }
      }'

Updatable: name, company, phone, email, address, city, state, pincode, source, stage, expected_value, expected_close_date, notes, lost_reason, custom_fields, assigned_to. Errors: 401 invalid/revoked key, 403 organisation frozen, 404 lead not in your organisation, 400 invalid body.

API — Wallet Balance

Poll before bulk operations to avoid mid-batch failures.

{
  "organisation_id": "…",
  "organisation_name": "Acme Steel",
  "wallet_balance": 8420,
  "is_frozen": false,
  "low_balance": false
}

curl https://<your-app-domain>/api/public/v1/wallet \
  -H "X-API-KEY: sk_live_xxx"

API Walkthrough — End-to-End Example

This walkthrough replays the Acme Fabrics scenario using real HTTP requests. Public REST endpoints cover master data (products, parties, vendors) and wallet reads. QR generation, delivery challans, invoices, payments, and ledgers currently run inside the app (buttons in the UI or authenticated createServerFn calls); each step below shows the exact in-app action and the credit it costs, so you can script the API parts and drive the rest from your ERP UI. Replace <host> with your app domain and export your key first:

export TRAKOR_HOST="https://<your-app-domain>"
export TRAKOR_KEY="sk_live_xxx"   # Settings → API keys

Step 1 — Check wallet balance before you start

Poll once so you know a big batch (e.g. 500 QR codes = 500 credits) will not run out mid-way.

curl -s "$TRAKOR_HOST/api/public/v1/wallet" -H "X-API-KEY: $TRAKOR_KEY"

# → { "wallet_balance": 12000, "is_frozen": false, "low_balance": false }

Step 2 — Upsert a vendor (Northline Steel Mills, Maharashtra)

curl -s -X POST "$TRAKOR_HOST/api/public/v1/vendors" \
  -H "X-API-KEY: $TRAKOR_KEY" -H "Content-Type: application/json" \
  -d '{
    "name": "Northline Steel Mills",
    "gstin": "27AAAAA0000A1Z5",
    "state": "Maharashtra",
    "phone": "+91 98765 43210",
    "email": "sales@northline.example"
  }'

# → { "id": "…", "name": "Northline Steel Mills", "created": true }

Step 3 — Upsert a customer party (Acme Retailers, Karnataka)

curl -s -X POST "$TRAKOR_HOST/api/public/v1/parties" \
  -H "X-API-KEY: $TRAKOR_KEY" -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Retailers Bengaluru",
    "contact_info": "Priya | +91 90000 11111 | priya@acme-retail.in"
  }'

GSTIN and State can be set from /parties after creation; the intra-state Karnataka party will pick CGST + SGST automatically at invoice time.

Step 4 — Upsert a product (Cotton Roll 40s, 18% GST)

curl -s -X POST "$TRAKOR_HOST/api/public/v1/products" \
  -H "X-API-KEY: $TRAKOR_KEY" -H "Content-Type: application/json" \
  -d '{
    "name": "Cotton Roll 40s",
    "description": "HSN 5208 · UoM PCS · 18% GST · price exclusive",
    "price": 850
  }'

HSN, UoM, GST % and inclusive/exclusive flag are edited in /products. Once set, they drive tax on every downstream document.

Step 5 — Generate QR codes (in app)

Open QR → Generate, pick Cotton Roll 40s, quantity 100. Costs 100 credits(1 credit per QR). Wallet drops from 12,000 → 11,900. Print fromQR History(select rows → Download QR Codes → A4 PDF, 24 per page).

# Re-check wallet after batch
curl -s "$TRAKOR_HOST/api/public/v1/wallet" -H "X-API-KEY: $TRAKOR_KEY"
# → { "wallet_balance": 11900, ... }

Step 6 — Purchase Invoice from Northline (inter-state, IGST)

Purchases → New: vendor Northline Steel Mills, add Cotton Roll 40s × 100 @ 700. Vendor state (Maharashtra) ≠ org state (Karnataka), so Trakor applies IGST 18%. Costs 1 credit. Wallet: 11,899.

Step 7 — Delivery Challan for Acme Retailers

Challans → New: party Acme Retailers Bengaluru, scan the 100 printed QR labels (each scan beeps and adds qty 1), Save. Costs 1 credit. Wallet: 11,898.

Step 8 — Convert Challan → Sales Invoice (intra-state, CGST+SGST)

Open the saved challan → Convert to Invoice. Karnataka → Karnataka triggers CGST 9% + SGST 9%. Add E-way bill / IRN if applicable, Save. Costs 1 credit. Wallet: 11,897.

Step 9 — Record a partial payment

Open the invoice → Record payment → part-amount (e.g. ₹50,000 of ₹1,00,300). Status flips to Partial on /invoices.

Step 10 — Reconcile the customer ledger

/ledgers→ row action Ledger → pick date range → Download PDF / Export XLS. Debit shows the invoice, Credit shows the payment, running balance = ₹50,300 outstanding. Purchases and payments made appear in the same statement — one ledger per contact.

Credit summary for this walkthrough

Rates come from credit_pricing (your Reseller can override defaults). Poll /api/public/v1/wallet before large batches and use/settings/api-keysto rotate the key if it leaks.

HTTP Error Codes

Webhook & Push Integration Guide

To push data from your third-party app whenever a product, party, or vendor is created/updated, fire outbound HTTPS requests to the endpoints above. Recommended pattern:

1. Generate an API key in Settings → API Keys, store as a secret.
2. Poll GET /wallet before bulk pushes; abort if wallet_balance is too low.
3. On product.created/product.updated → POST /products.
4. On party.created/customer.updated → POST /parties.
5. On vendor.created/supplier.updated → POST /vendors.
6. Treat HTTP 2xx as success. On 5xx retry with exponential backoff (1s, 5s, 30s, 5m).
7. All POST endpoints are idempotent by name — safe to re-send.

const items = await myErp.getProducts();
for (const p of items) {
  await fetch("https://<your-app-domain>/api/public/v1/products", {
    method: "POST",
    headers: {
      "X-API-KEY": process.env.LOVABLE_API_KEY,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      name: p.title,
      description: p.notes,
      price: p.unit_price,
    }),
  });
}