# Network sync: how it works

_How TecPet copies the head office's catalog and rules to the branches, keeping the whole network standardized._

> **💡 Tip**
>
> Whenever you change the catalog at the head office (a price, a new combo), remember to **run the sync** so the branches get the update. And create local items on a branch only when they're truly exclusive to that unit.

In a network, the **head-office account** is the **source of truth**: it defines the catalog (services, combos, plans) and the general rules. The **sync** is what copies these definitions from the head office to each **branch**, keeping the whole network standardized — without re-registering everything store by store.

## It always goes from head office to branches

The sync runs in **one direction only: head office → branches**. The head office sets the standard; the branches receive it. There's no "reverse" — a branch doesn't change the network's catalog.

## What gets synced

The network defines **which items** are included in the sync. The available types are:
- **Services** and [Service categories](/en/configuracao/cadastros/categorias/) (with their **price tables**);
- [Combos](/en/configuracao/cadastros/combos/) and **Plans**;
- **Payment methods**;
- [Checklists](/en/configuracao/geral/checklists/);
- [Species & Breeds](/en/configuracao/geral/especies-e-racas/);
- [Notification templates](/en/configuracao/geral/notificacoes-automaticas/) and their **triggers/schedules**;
- [Pet Care](/en/configuracao/pet-care/o-que-e-pet-care/): categories, document templates and applications/vaccines;
- **Segments** and [Advanced settings](/en/configuracao/avancado/configuracoes-avancadas/).

What's **not** synced is up to each unit — for example, the store's own **staff** and **information**.

## How it works in practice

When the sync runs, each branch receives a **mirrored copy** of the head office's items:
- If the item **doesn't exist yet** on the branch, it's **created**;
- If it already exists (because it came from the head office before), it's **updated** to match the head office's (name, price, description, etc.).

Each copy stays **linked** to the original item at the head office, so the next updates find the right copy and keep it current.

## Items created on the branch itself are preserved

If a branch creates an item **locally** (one that didn't come from the network), the sync **does not overwrite** it. Only items that **came from the head office** are updated. That way a unit can have something of its own without fear of losing it on the next sync.

## When the sync happens

The sync runs:
- When **setting up the network** — when a store becomes the head office or when a store is **linked as a branch**, it immediately receives the head office's catalog;
- When the **team triggers the sync** (via network management / with support). It can be triggered for **the whole network** or for **a specific unit**.

## A branch can be left out

Each branch has a **sync switch**. If it's off, that unit **does not receive** the head office's updates — useful for special cases where the store needs a separate setup.

## WhatsApp: shared or individual

The network also defines how **WhatsApp** works:
- **Shared** — one service number for the whole network;
- **Individual** — each unit with its own number.

👉 To understand the screen differences between head office and branches, see [Network: head office and branches](/en/operacao/dashboard/rede-matriz-e-filiais/).

## For your account type

### Head office
You're on the **head office**: what you register here (services, combos, plans, etc.) is what gets **mirrored to the branches** when the sync runs. Think of the head office as the network's "master template".

### Branch
You're on a **branch**: the catalog and rules arrive **ready from the head office**. You don't edit those items here — but items you create **just for your unit** stay yours and aren't overwritten.

### Single store
You have a **single store**: it's not part of a network, so **there's no sync** — everything you register applies only to your store.

---
_feature: rede-sync · atualizado em 2026-06-09 · fonte: https://help.tec.pet/en/operacao/dashboard/sincronizacao-da-rede/ — TecPet Central de Ajuda_