Business Tools · Across the office
Your own software, joined to your office on a key you issue
Connect your website or your own software to KaryalayOne for one branch, and switch each kind of record — catalogue, stock, orders, leads — on or off.
What it does
The key, what it can reach, and what the office tells your software
One key for each website or piece of software, issued in the office for one branch — and what you see of its use.
A key you issue
- Made in the office
- Give the address of your website or your own software. It is tested before a key is issued.
- When the test fails
- Software the test cannot reach can still have a key, and the connection is marked unverified.
- A key and a secret
- The secret is shown once and cannot be shown again, so copy it then. The key’s last four characters stay on view.
- One branch
- A key belongs to the branch you are working in when you issue it, and reads that branch’s records.
- Taken back
- Take a key back and its access stops at once, for good.
- Who issues them
- The owner, admins and branch managers, and anyone you give the website access role.
What it can reach
- Your branch
- Its address, contact details, logos, legal name and tax IDs.
- Catalogue and stock
- Items with their images, HSN codes, GST rates, variants and every price list; stock per warehouse, batches and the movement ledger. Cost price stays out unless the branch shows it.
- Customers and papers
- Customers and their contacts, quotations, invoices with what is paid and due, payments, orders with their shipments, and requests you can price.
- Projects
- Tasks, deliverables, approvals, the team, comments and time logs.
- Sent in
- New leads into CRM, answers to your forms, requests you can price, and checkouts that raise an order and its invoice — every line priced again in the office.
- A switch for each
- Each kind is switched on or off whole. Leads, forms and storefront requests have one switch for reading and one for sending in.
- On to begin with
- A new key starts with every kind switched on. You switch off what your software should not have. Leads also wait for the connection’s lead setting, which starts off.
The office tells your software
- If you ask it to
- Give the office an address to tell. It is tested before telling is switched on.
- An item changes
- A catalogue item is created, edited, removed or restored.
- An order moves
- An order is placed, or its status changes.
- A lead is worked
- Updates on the leads your software sent in.
- Tried again
- If your software does not answer, the office tries again with a growing wait, and shows what still failed, with a retry.
Keeping an eye on it
- Kind by kind
- When each kind of record was last used, with its calls and its errors.
- Leads
- Leads received, in all and over the last seven days, and updates still waiting to go back.
- What was sent
- The recent messages the office sent your software, and which of them failed.
- Pace
- Each key answers up to 120 times a minute.
- Switched on
- Switched off
Switches
One key, switched kind by kind
A row for each kind of record, each with its own switch. The three that take records in have a second switch on the right, for sending in.
Issued for one branch
The key is made in the office for the branch you are working in. Its secret is shown once; the last four characters stay on the card.
Everything on to start
A new key reaches every kind of record, from branch information down to storefront requests — reading, and sending in where a kind takes records in.
Switched off, kind by kind
You switch off what your software should not have. Here it keeps the catalogue, stock, orders, leads and storefront requests, and loses customers, quotations, invoices, payments and projects. Forms it may read but not send answers to.
Taken back at once
If the software is retired or the secret gets out, take the key back and its access stops. A key taken back is not switched on again — issue a new one.
Hand-offs
Connections with leads, the catalogue, orders and forms
What passes over a key into the parts around it, and where to read about each.
Lead sync from your own systems →
The leads kind of the same key: each lead lands in CRM with the source, status and owner set on the connection, and a guide shows your developer how.
Catalogue →
Items, variants, images and price lists are read from here, and an item saved here is one the office can tell your software about.
Orders →
A checkout sent in becomes an order here, with its invoice, and the office can tell your software when an order is placed or moves on.
Forms →
Your software reads your active forms and sends answers into the Forms inbox, each checked against its form.
Your website holds the same kind of key — how your website reads your records.
Leads that collect in a Google Sheet come in through Lead sync from a sheet instead.
What it costs
What your own connections cost
Connecting comes with whichever sets you choose. What is priced is the monthly allowance of requests from your own systems.
Requests from your own systems
50,000 a monthincluded, for the whole business
More in blocks of 50,000 a month, at ₹200.00 a block a month.
Prices exclude GST.
- Included with every set
- Connecting has no price of its own. It comes with whichever sets you choose.
- As many connections as you need
- Issue a key for each website or piece of software.
- An allowance for the whole business
- Every key shares it, and more is added in blocks on the pricing page.
Before you start
Questions about your own connections
What a business asks before it gives its software a key — including where the answer is no.
No to both. A key works until you take it back, and its secret cannot be changed or shown again. To replace one, take it back and issue a new key, then put the new key and secret in your software.
No. There are no ready-made connectors to them or to other marketplaces. Your own software, or your developer, uses the key directly.
No. What limits a key is the one branch it belongs to and the kinds of record you leave switched on. If it is ever in the wrong hands, take it back and its access stops at once.
Not one by one. For each kind of record, the connection shows when it was last used, with its calls and errors, along with the leads it sent and the recent messages the office sent back.
For leads, yes. A guide inside the office, filled in with that connection’s own address and key, has code to copy for PHP, WordPress and Node, and a command to try it from a terminal. It covers sending leads, hearing back as they are worked, and what to do when a request fails.
No. A key belongs to the branch you are working in when you issue it, and reads that branch’s records. For another branch, switch into it and issue a key there.
See your own connection in it
Bring the software you want to connect to the demo, and we will issue a key, switch off what it should not have and go through the guide with you.