The path that works today is importing your catalog from a CSV or Excel file. Per-system automatic mappers (Loyverse, Alegra, Siigo, World Office) are on the roadmap; for now you export to CSV from your system and import that into Puntovivo.
From your current system, export the catalog to CSV or XLSX. It must include SKU or barcode, description, cost, price, VAT and stock per site.
Puntovivo deduplicates by barcode and then by SKU. If you sell by weight or by unit, leave the matching column marked. Delete discontinued products before importing.
From the console, open Settings → Import. Drop the CSV with the expected headers and confirm the column mapping field by field before continuing.
Before applying, you'll see the summary: how many new products, how many will be updated, how many need your decision. Approve in batches — nothing is applied until you confirm.
Do a physical count of the main site and compare it against the imported balance. The first register opening uses the base you define, not the imported balance. From there on, the flow is normal.
This is what automatic mapping will look like when it lands: the wizard would recognize these columns without you renaming anything. For now you export to CSV and match the headers to the format below.
One sheet per site, headers in the first row, UTF-8. Copy this example and replace the data.
sku,barcode,descripcion,costo,precio,iva,unidad,categoria ARQ-12-PV,7705412000123,Arepa de queso · Pack 12,5800,9500,5,unidad,Panadería CAF-500-TIN,7702045009982,Café tinto molido 500 g,12200,19900,5,unidad,Bebidas BLS-M-RCY,7705781100456,Bolsa reciclable mediana,420,1200,19,unidad,Empaque LCH-1L-LV,7702521011234,Leche larga vida 1 L,3400,5400,0,unidad,Lácteos HRN-1K-MAZ,7705412009870,Harina de maíz blanca 1 kg,3100,4900,0,unidad,Granos
If your export has an odd structure, open an issue on GitHub with a sample (no sensitive data) and we'll work through it in the open.