New 2026-10-07: product sync with Xero is genuinely two-way. This page didn’t exist before, and the fields below go further than the one-way “FikaTrade creates invoices in Xero” behaviour described elsewhere in the Invoicing guide.
What syncs, and which way
Name, description, cost price, sale price (your base price) and availability are compared between FikaTrade and Xero. A change on one side that the other side hasn’t also changed is applied automatically if you’ve turned the matching Update automation setting on (see Connect FikaTrade to Xero); otherwise it’s a finding for you to decide on the Sync screen. If both sides change the same field, that’s always a decision — different fields changing on each side merge automatically. Categories never leave FikaTrade. Xero has nowhere to hold them, so they’re not part of the comparison at all — see Manage categories.At first match
When a product and a Xero item are first linked (by matching code):- If one exists only in Xero, you’ll see it as a finding — add it to FikaTrade, tell FikaTrade this one’s not yours, or keep it permanently out of sync.
- If one exists only in FikaTrade, the finding is the mirror image — create the matching item in Xero, or keep it out of sync.
- If a required value (like a price) is missing on one side, that also shows as a finding to resolve or dismiss.
What only happens once, at creation
Tax setting and sales account code are read from Xero (or set from FikaTrade) only when the link is first made. Changing either one directly in Xero afterwards won’t be picked up — FikaTrade’s copy stays as it was set at creation. See Xero mappings.Limits when sending to Xero
- A product code longer than 30 characters is never sent to Xero.
- A product name longer than 50 characters is truncated when sent to Xero.
- FikaTrade won’t clear an item’s sale price in Xero to blank.
- If a product’s code is changed, that’s flagged as a finding you can dismiss — it isn’t automatically re-linked to a different Xero item.

