Deleting a branch

Deleting a branch is a clean operation: it only goes through when nothing is left pending in it. Before asking you to confirm, the screen shows you exactly what's blocking it and what will happen if you continue. This article explains every blocker, how to resolve it, and the real effect of the delete on warehouses, registers, and people.

Reading time: ~6 min

When to use this

• You're about to delete a branch and want to know what Mosce ERP checks before letting you continue.
• The delete dialog shows a notice blocking the delete and you don't know how to resolve it.
• You want to understand ahead of time what happens to the warehouses, registers, and assigned people when a branch is deleted.

Before you start

• You need the branches:delete permission to delete a branch, from Settings → Branches.
• If you're not yet familiar with how branches work, start with Branches: what they are, who gets into each one, and how many your plan allows.

---

A clean operation, not a forced removal

Before letting you delete a branch, Mosce ERP checks everything that could be left pending or inconsistent if it did. If it finds anything, the delete is refused and it tells you exactly what it is and how much of it there is - never a generic "cannot be deleted" message. If it finds nothing pending, it still shows you what's about to happen before you confirm, so you decide with the full picture in front of you.

What can be blocking the delete

Stock in its warehouses

If any warehouse of the branch still holds stock, the delete stops. You need to transfer it to another warehouse or adjust it before continuing.

Negative balances

A negative balance isn't the same as having no stock: it means an operation is still waiting on a restock or an adjustment. Mosce ERP treats this as a separate blocker because, if you let it slide, you would lose that pending history without noticing. Resolve it with a restock or an adjustment before deleting the branch.

Orders pending collection

Any order from the branch that hasn't been collected yet stops the delete. Collect it or cancel it first.

Orders not yet invoiced

An order that hasn't been invoiced yet also stops the delete, even if it's already been collected. Invoice it or cancel it before continuing.

An open cash-register shift

If any register of the branch has an open shift, you need to close it before you can delete the branch. See Cash register.

Products linked to the warehouse, even at zero

A product can stay linked to the branch's warehouse even when its balance sits at exactly zero - for example, if it ever had movement there. Mosce ERP counts that the same as a blocker, because sitting at zero isn't the same as "was never there." Unlink the product from that warehouse before deleting.

Products that have that warehouse as their default

If a product has this branch's warehouse configured as its default warehouse, you need to reassign it to another warehouse. This isn't the same as moving merchandise: it's only changing which warehouse that product uses when a document line doesn't specify one. See Warehouses for more on a product's default warehouse.

Purchases pending receipt

A purchase still waiting to be received against this branch's warehouse stops the delete. Receive it or cancel it first.

Being the default branch

You cannot delete the branch marked as your business's default. Mark another branch as the default before trying again.

What happens when the delete goes through

Once nothing is left blocking it, confirming the delete does this:

• The warehouse that was born with the branch gets deleted - the one Mosce ERP created automatically when you set the branch up.
• The branch's other warehouses lose their branch. They keep working for receiving purchases and for transfers, but not for selling, until someone assigns them a branch again from their own record.
• The branch's cash registers get deleted. Their shift and reconciliation history can no longer be reviewed, though the accumulated totals still show up in the point-of-sale report.
• People assigned only to this branch are left without a branch. They won't be able to work in Mosce ERP until an administrator assigns them another one from Settings → Branches. The screen shows you the exact number of people affected before you confirm, so it isn't a surprise afterward.

Documents already issued are kept

Deleting a branch doesn't erase its history. Orders, invoices, and other documents already issued from that branch keep existing, and you can keep reviewing them from the all-branches view - the only way to look back at the history of a branch that no longer exists as an active option.

Common mistakes

Frequently asked questions

Can I recover a branch after deleting it?

No. Deleting a branch isn't reversible from the interface. If you need to keep operating at that location, you'd need to create a new branch.

Do I lose the sales history of the deleted branch?

No. Documents already issued are kept, and you can still review them from the all-branches view even though the branch no longer exists as an active option to pick.

What happens to people who were assigned to several branches, including the deleted one?

They're not affected. Only people who had this as their only assigned branch lose access; anyone with access to others keeps working normally in them.

Can I choose which warehouses get deleted and which are kept?

Not directly from the branch delete. Only the warehouse that was born with the branch gets deleted; the rest automatically lose their branch and are kept. If you want to delete any of those other warehouses, do it separately from Inventory → Warehouses after clearing its stock.

Related

• Branches: what they are, who gets into each one, and how many your plan allows
• Viewing every branch at once
• Warehouses
• Cash register
• Inventory is per branch too

---

Last updated: 2026-09-09