Data Requirements and Setup
Where TicoSync expects customer identity, CABYS, HS code, and shop issuer data to live in Shopify.
Customer Identity
- Domestic FE uses customer metafield hacienda.structured_cedula.
- Optional domestic activity code uses hacienda.structured_ciiu.
- Export invoices use customer metafield ticosync.tax_id, shown in Shopify as Tax ID/Passport.
Export Identity Fallback Order
- ticosync.tax_id
- Billing phone
- Shipping phone
- Order phone
- Customer phone
Tax ID/Passport is cleaned to letters and numbers only. Phone fallback is cleaned to digits only.
CABYS
- TicoSync looks for hacienda.structured_cabys on the variant first.
- If the variant does not have it, TicoSync falls back to the product.
- Missing CABYS can cause Hacienda rejections or incorrect tax classification.
HS Code for Export
- Export goods lines use Shopify's standard customs HS code from the variant inventory item.
- If Shopify has a destination-country specific customs code, TicoSync prefers that value.
- TicoSync pads short HS code values with zeros on the right to produce the Partida Arancelaria sent in export XML.
Shop-Level Config
- Issuer identity, activity code, signing credentials, PDF header text, and related Hacienda settings are managed in the Configs page.
- International Optional Header Text is used on export PDFs instead of the normal Optional PDF Header Text.
Operational Guidance
When a document fails, the first things to verify are customer identity, CABYS, HS code for export goods, and whether the order was fulfilled with the correct items and quantities.