Multi-Domain and QuickBooks

[lesliekirk]

I did a little reading ahead of time, and if a store is using the Miva QuickBooks Online module, the docs for it have a note that says "Only one QuickBooks Online company can be connected to a Miva store at a time." How does this work with a Multi-Domain store? I asked the Support Docs AI. It basically told me to contact Miva Support.

The store I'm working with is currently using the T-Hub connector, and it could be worth changing to the MivaConnect QBO configuration if it can import orders and inventory from the two stores into one QB account.

[Rick Wilson]

The clue is in the term Store. Multi-Domain where it's many domains to a single "store" will only install to one QBO instance.

Multi-Domain where you're using Additional Storefronts, each store can connect to a different QBO file.

[lesliekirk]

Multi-Domain where you're using Additional Storefronts, each store can connect to a different QBO file.

Can, but does it have to? The store owner wants to connect the main store and the additional store to the same QBO file. Each store will be using the same products (except at different price points). She would also like the ease of having all invoices in one instance of QBO.

FYI, we've already been down the "Unified Stores fronts under one Primary Store" road, and it will not work for this store as it needs the ability to have the same products (codes) being offered at different price points. Brennan already advised me that using Price Groups would not be an option.

[Rick Wilson]

Yes — both Additional Storefronts can connect to the same QBO file.

Product just confirmed for me: orders flow into the one QBO instance, the prefix differentiates them, and it works just fine.

The one thing to set up deliberately, given you're running the same product codes at different price points: turn off the QBO to Miva product sync options in both stores' QBO module settings ("New products in QuickBooks are automatically created in Miva" and "Product changes in QuickBooks are automatically synced to Miva"). With those on, a product change flowing through QBO from one store will overwrite the matching record, including price, in the other. Miva to QBO push is fine.

You just don't want QBO writing back to Miva. Same applies to the customer auto-update options.

Set it up that way and you should gets exactly what you're asking for: one QBO file.