If you trade from more than one place, Finocket can hold each one as its own shop — with its own code, address, opening hours, manager and tills. Once a shop exists, you can open the next one by copying it, instead of setting everything up again.
A shop is not a godown
These are two different things and Finocket keeps them apart on purpose. A shop sells; a godown holds stock. A shop usually has a godown, a warehouse is a godown with no counter, and a pop-up might share another shop’s godown entirely. So a shop points at a godown rather than owning one — and two shops are allowed to point at the same one, if that is really how you work.
This matters because if two shops shared a godown by accident, their stock would be added together and every per-shop stock figure you looked at afterwards would be wrong.
Shop codes
Every shop needs a short code — MAIN, MG-ROAD. Codes are turned into capitals and must be unique within your workspace, so “main”, “Main” and “MAIN” are one shop rather than three. The same code in a different workspace is fine.
Opening the next shop
Through the API, name the shop to copy and give the new one a name and a code, and Finocket sets it up with the same shape: the same kind, region and opening hours, a bill series of its own, and the same number of tills.
Its bill numbering starts again at 1, under its own prefix. That is deliberate — if two shops shared one numbering, their bills would interleave and neither would have the continuous run a GST audit expects to see.
What a new shop does NOT inherit
Three of these would be expensive to discover later, so Finocket refuses to copy them and tells you it has refused:
- The godown. A new shop holds its own stock. Pointing it at the old shop’s godown would merge the two shops’ inventory.
- The UPI ID and payee name. Takings must never be routed to another shop’s account by a default nobody chose.
- Stock, staff, price lists and access. A new shop starts empty and is received into. Price lists and who-can-do-what are set for the whole business, not per shop, so the new shop already has them.
The list of what was skipped comes back with the result, so you never have to assume.
If it stops half way
Run it again. Setting up a shop is done in steps, and each step checks whether it has already happened — so a second run finishes what is missing rather than starting over or making duplicates. The result tells you whether it created the shop or resumed one.
The roster
Who works at a shop is recorded as a period, with a start date and an end date, rather than a simple on/off. When somebody leaves, their posting is closed with a date and the record stays. That is what lets you answer “who was on that till in June” months later — a question that comes up whenever stock or a refund needs explaining.
What this does not do yet
Shops are set up on the Shops screen and each till is posted to one, so a sale carries the shop it was rung up in, and Retail intelligence reads sales, stock and customers per shop. To open the next shop from an existing one, choose Add a shop and pick the shop to copy from — its tills, price list and numbering come across; stock, staff and sales never do. The same copy is available to integrators as POST /v1/stores/provision.