Can any employee add a shop?
No. The action depends on permissions and available plan capacity.
Multiple Fertilizer Shops: Scope and Access
Short answer
Managing multiple shops requires clear transaction scope. Confirm which shop is active before entering a purchase, sale or expense and before reading a report. Kroply’s organization shop setup depends on permissions and plan capacity; a second godown and a second business shop are different decisions.
Decide whether you need a shop or a godown
A godown describes a stock location, while a shop defines the business context in which staff enter and review transactions. Write down where goods are stored, where sales are recorded and which staff need access before configuring either. Do not create extra shops simply to label shelves or storage rooms.
Review capacity and permissions
On the web app, open Organization and its Shops section with a permitted account. Review existing shop names and addresses before adding another. Shop, staff and OCR allowances depend on the current plan; access also depends on user permissions. Check the current plan details when an action is unavailable rather than assuming every subscription includes unlimited shops or staff.
Verify staff access with their own accounts
Set the intended role permissions and confirm staff can access the shop they need. A person who can create sales may not need access to profit or organization setup. Test the normal task with that person’s account and resolve access through the authorized controls instead of sharing another login.
Worked shop-scope example
Illustrative example: Shop A receives ten bags and Shop B sells two bags from its own stock. Before saving each transaction, confirm the intended shop. Recording the Shop B sale while Shop A is active gives the wrong operational context even if the product names match. Afterward, review the source records in the intended shop rather than trusting a combined handwritten total.
Compare reports on the same basis
Choose the same period and report settings for each shop before comparing activity. Keep the shop name with each exported file or review note. Investigate a difference through the underlying invoices and payments. Do not assume every report is an organization-wide consolidation or add unlike summary figures together.
Treat stock movement as its own workflow
A physical movement needs an appropriate recorded movement with clear origin and destination. Follow the supported godown transfer instructions for that scope. Do not assume that a godown transfer automatically represents every inter-shop transaction. Confirm the supported handling for the intended shops and review the resulting stock before the goods are used in billing.
Questions and answers
Is a godown the same as a separate shop?
No. Define the business and storage scope first, then use the relevant setup and supported movement workflow.
Related resources
- Multiple-shop capabilities
- Manage organization shops
- Set staff permissions
- Godown setup and stock
- Handover between operators
How Kroply handles this
Kroply provides connected shop billing, inventory, supplier records, reviewable OCR, customer credit, expenses and reports. Core workflows require internet, and staff and shop allowances depend on the current plan.
Things to consider
Test your own purchase, sale, receipt and return. Compare devices, printing, languages, migration scope, current pricing and support channels using the same requirements.