Cin7 Core and QBO Account mapping

kylenash

We are noticing that Cin7 Core's product level mapping is being overwritten by QBO's mapping of those same products. This is counter-intuitive as the product level mapping in Cin7 Core should be preserved through the integration's sync. 

 

Please can the integration be updated to maintain and respect the mapping of products and services in Cin7 Core. This is especially important as products can only have a single income or expense account in QBO. If the same SKU is sold in different channels QBO overrides the mapping there.

3

Comments

4 comments

  • Comment author
    ryanbehnken

    Yes, please! This request makes perfect sense. Product level mapping should be preserved and held through the products' movements rather than being recategorized by QBO. 

    0
  • Comment author
    Nicolas Noakes

    What do you mean by the “product level mapping”? What data fields are you referring to?

    0
  • Comment author
    Andrea Dugas

    I like this topic. We are new, but working on mapping right now

     

    0
  • Comment author
    omar

    I Ran into this during a Cin7 Core + QBO implementation. A few things that helped:

    1. Decide which system owns the accounts. Cin7 Core should be the source of truth for revenue/COGS/inventory accounts. In QBO, avoid editing income/expense accounts on synced items, because changes there can conflict with what Cin7 posts.
    2. Map at the right level. If one SKU sells through several channels and you need separate revenue lines, product-level accounts won't do it. Use channel/sale-level revenue accounts or QBO Classes/Locations for channel reporting instead of splitting by product account.
    3. Test before go-live. Post 2–3 test sales per channel, then check the QBO journal and P&L by class to confirm each landed where expected.
    4. Document the mapping in a simple sheet (product category → inventory/COGS/revenue account, channel → class) so new SKUs get set up the same way.

    @Andrea Dugas, since you're mapping now: lock down point 1 before you sync history, it saves a lot of cleanup later.

    I do Cin7 Core + QBO implementations, so happy to compare notes if you get stuck.

    0

Please sign in to leave a comment.