Opening a second countertop location: the records that must work across both
Define which decisions belong to each branch and which are shared. Test inter-branch jobs, material transfers, access and reporting before making the second location dependent on the same systems.
Define which decisions belong to each branch and which are shared. Test inter-branch jobs, material transfers, access and reporting before making the second location dependent on the same systems.
Decide what the second location does
A showroom, a warehouse and a second fabrication plant create different information needs. Write down where sales, templating, cutting, installation and customer communication will happen. A second address in a customer database is not a complete operating model.
For each stage, identify who can commit a date or change the work. If one branch sells a job that another produces, both need a shared understanding of readiness and capacity. Define how a request becomes a confirmed production commitment and who communicates a change to the customer.
Give shared records clear owners
Decide whether pricing, materials, customer identities and job statuses are centrally maintained or branch-specific. Document legitimate local variations. Two locations can use different selling prices while still needing consistent material identities and reporting definitions.
Assign responsibility for correcting shared data. Without that ownership, a branch may create a second customer or material record simply to get through the day. Establish a way to resolve the issue while preserving the work already associated with the original record.
Demonstrate the cross-branch exceptions
| Scenario | Question for the system demonstration |
|---|---|
| Sell at A, fabricate at B | Who owns the job and production commitment? |
| Transfer a slab | When is it unavailable at A and received at B? |
| Move an installation crew | Which calendar and customer notice change? |
| Restrict commercial information | Which roles can see pricing and reports? |
| Correct a shared record | What history remains after the correction? |
Do not infer multi-location support from a product’s general scheduling claim. Ask the vendor to run these scenarios in the exact configuration proposed. Record whether the solution uses standard settings, separate accounts, integrations or custom development.
Make reports comparable
Agree on the meaning of a booked job, completed job, callback and material allocation. If one branch counts installation while another counts invoicing, their completion totals are not directly comparable. Preserve definitions alongside the report.
Keep local operating views as well as a combined summary. A healthy total can conceal a blocked branch. The people managing a location need to see their own queues and exceptions without reconstructing the company-wide report every morning.
Test the absence of the owner
Have the managers walk through an ordinary day and one difficult exception without relying on the founder to resolve every ambiguity. Record the decisions that still return to one person. Those are candidates for clearer authority, training or a defined escalation path.
Use the opening checklist to assign each unresolved item an owner and a practical acceptance test. The software can support the arrangement, but the operating responsibilities must be explicit first. A second location becomes manageable when the records, commitments and decision rights travel reliably between people who are no longer standing in the same room.
Sources and product records
- Moraware: Product overview
- Moraware: Systemize API introduction
- ActionFlow: Solutions and package descriptions
- StoneGrid: StoneAPP product overview
Working references
Browse the product comparison register · How we evaluate evidence · Interview and demonstration worksheets
Software options to evaluate
Use the same practice job and acceptance criteria for each proposed configuration. These brief descriptions reflect vendor documentation, not independent test results.
- ActionFlow — fabrication workflow packages.
- Horus — slab tracking and layout tools.
- Moraware — quoting, scheduling and inventory products.
- SlabOS — a platform spanning drawing, quoting, inventory, nesting, scheduling and field work. Platform documentation.
- SlabWise — quoting, DXF and fabrication workflows.
- StoneAPP — fabrication business management.
- Stone Profit Systems — fabrication ERP and material records.
Confirm current modules, versions, data exports and implementation scope directly. Open the software comparison register.
Product records for this article
- Systemize — sources, check date and demonstration questions
- Inventory — sources, check date and demonstration questions
- ActionFlow — sources, check date and demonstration questions
- StoneAPP — sources, check date and demonstration questions
Original editorial evaluation framework. Product-specific descriptions are attributed to vendor documentation; no independent test, interview or survey result is claimed. Examples and proposed exercises are illustrative.
Editorial approach & corrections →