Skip to main content

QuickBooks Online Integration

Connect QuickBooks Online (QBO) to Logiwa to synchronize orders, products, inventory, purchase orders, fulfillment, and billing.

Connect QuickBooks Online (QBO) to Logiwa to synchronize orders, products, inventory, purchase orders, fulfillment, and billing.

Logiwa streamlines your warehouse management with a user-friendly self-onboarding process for sales channels. This integration connects a QuickBooks Online company file to Logiwa for order import, invoicing, inventory adjustments, purchase order sync, and receiving/billing workflows.

Before You Begin

  • A QuickBooks Online account with Admin credentials.

  • A dedicated “bridge application” created in the Intuit Developer Portal, generating a Client ID and Client Secret.

  • The Logiwa Client, Warehouse, and Shipment Order Type that should be used for this connection.

  • A Product UOM value that matches exactly (case-sensitive) between QBO and Logiwa.

  • If billing/inventory adjustment mapping is needed, plan to complete Reason Code to Adjustment Account mapping after the connection is activated.

⚠️Multi-warehouse setup: If you operate more than one warehouse, a separate QBO Store connection must be created for each warehouse. There is no single connection that spans multiple warehouses. Each connection maps 1:1 to one Warehouse field and should be configured independently, including its own Client ID/Secret entry and flow selection.

⚠️Production keys only: This integration only supports Production keys. There is no Sandbox option. UAT testing (see the Go-Live checklist below) runs against your live QBO company file, not a sandbox environment.


Create a Bridge App in the Intuit Developer Portal

This one-time setup must be performed by a user with QuickBooks Admin credentials.

  1. Go to developer.intuit.com and sign in with your QuickBooks Admin account.

  2. Click MyHub > App Dashboard, then click + Create an app.

  3. Enter a recognizable app name (for example, Logiwa WMS Integration).

  4. Under Select Scopes, check Accounting. This grants permission to sync orders, invoices, products, and inventory.

  5. Click Create App.

  6. In the app’s left sidebar, go to Keys & credentials under Production Settings.

⚠️Use Production keys, not Sandbox/Development keys, for live operation. Complete any business verification details Intuit prompts for.

  1. Locate and copy the two credentials:

    • Client ID: a unique string of characters.

    • Client Secret: click Show to reveal and copy this key.


Connect QuickBooks Online in Logiwa

  1. Log in to Logiwa and navigate to Integration Management > Store & Marketplace.

  2. Select QuickBooks Online Integration. The Connect QuickBooks Online Integration pop-up appears.

Connection Configuration

Field

Description

QuickBooks Online Store Name

Internal name for this connection within Logiwa.

Client

The Logiwa client entity these transactions belong to.

Warehouse

The specific warehouse tied to this connection (source of inventory operations).

Shipment Order Type

Default order type applied to imported sales orders.

Product UOM

Unit of Measure applied to all synced products under this connection. Entered once during setup and applied uniformly. It is not read per-product from QBO. Must match exactly across both systems (see Product UOM Formatting below).

Contact Email

Email address that receives integration notifications, status updates, and errors.

Client ID

The unique Application ID generated in the Intuit Developer Portal.

Client Secret

The secure key generated in the Intuit Developer Portal.

💡Credential note: You only need to enter your Client ID and Client Secret once, in this main pop-up screen. All individual workflow options enabled in subsequent steps automatically use these credentials.

Feature Selection

After clicking Continue, you’ll see the feature-selection screen.

  • By default, all integration flows are enabled.

  • You can toggle off any flow you don’t plan to use.

  • If unsure, leave all flows enabled. You can change these settings later via Manage Configuration.

Available flows:

  • Order Sync

  • Product Sync

  • Inventory Sync

  • Purchase Order Sync

  • Purchase Order Fulfillment / Receiving

  • Order Fulfillment

  • Billing Sync

ℹ️Independent flow toggles: Each flow above is independent and can be enabled or disabled on its own at any time via Manage Configuration. For example, Order Fulfillment can remain active while Order Sync is turned off. There are no mandatory dependencies between flows.

Authorize QuickBooks Online

  1. Click Continue after selecting your flows.

  2. You’ll be redirected to QuickBooks Online. Log in and select your company.

  3. Review the permissions requested by Logiwa, then click Authorize.

  4. You’ll be redirected back to Logiwa, where the store status shows Completed and Activated.

💡Post-installation configuration: Some flows require additional mapping after installation. For example, Inventory Sync requires Reason Code to Adjustment Account mapping, configured via Manage Configuration after the connection is activated.

⚠️Initial sync scope: On the very first run after activation, each flow only pulls records that match its active filters (for example, Purchase Orders with status “Open”). Historical records that don’t meet the filter criteria at that moment are not backfilled retroactively. If you have existing open transactions in QBO that you expect to see in Logiwa after go-live, confirm they meet the relevant flow’s filter criteria before activation.


Operational Rules & Edge Cases

Order Cancellation (“Voided” Invoices in QBO)

When an invoice is marked Void in QuickBooks Online, Logiwa handles the cancellation based on the order’s real-time fulfillment stage:

Fulfillment Stage

Logiwa Behavior

Created / Allocated

Logiwa automatically cancels the shipment order and releases allocated stock back to available inventory.

Shipped / Delivered

The cancellation request is rejected, and an exception event is logged.

Inventory Sync Scope

Adjustment-driven only: The Inventory Sync flow does not overwrite total available inventory line-by-line. It pushes finalized, unidirectional inventory adjustments performed in Logiwa to QBO.

Examples of adjustments:

  • Cycle counts

  • Damaged stock

  • Shrinkage

  • Receiving corrections

The adjustment is pushed to QBO using the mapped Reason Code.

Product UOM Formatting

⚠️Strict case sensitivity: Unit of Measure fields are strictly case-sensitive. If QBO uses EA and Logiwa uses ea or EACH, order synchronization will fail. Standardize all UOM values before turning on sync flows.

Product Deletion / Archival

  • If a product is marked Inactive in QBO, Logiwa updates the product status to Inactive.

  • If a product is permanently deleted in QBO, Logiwa does not delete the SKU.


Integration Flows & Field Mappings

ℹ️Reading these tables: Fields shown in parentheses are technical QuickBooks Online API names. The text before parentheses is the user-facing QBO label.

Order Sync (QBO to Logiwa)

Cadence & Trigger: Scheduled automation running every 10 minutes.

Business Rules: Pulls newly created, updated, or voided Invoices from QBO. Modified invoices update existing orders in Logiwa.

Source Field (QBO)

Target Field (Logiwa)

Logic / Notes

Customer Name

Customer / Company

Identifies the recipient customer in Logiwa.

Invoice Number

Channel Order Number

Serves as the primary reference number for fulfillment.

Item Name/Number

Line Item SKU

Non-inventory lines excluded.

Quantity

Pack Quantity

Total quantity of the item to be picked and shipped.

Private Note (“Voided”)

Order Status (Cancel)

Cancels corresponding order in Logiwa based on fulfillment status.


Product Sync (QBO to Logiwa)

Cadence & Trigger: Scheduled automation running every 15 minutes.

Business Rules: Synchronizes active products created or updated since the last sync. New items trigger product creation in Logiwa; existing items update price, cost, description, and status.

Source Field (QBO)

Target Field (Logiwa)

Logic / Notes

SKU

SKU

Primary unique product identifier in Logiwa.

Name

Name & Description

Mapped to both Product Name and Description fields.

Unit Price

Sales Price

Standard selling price for the product.

Purchase Cost

Purchase Price

Standard purchasing cost for vendor orders.

Active Status

Is Active

Syncs active/inactive status across systems.

⚠️Deletion rule: Deleted QBO products are never deleted in Logiwa.

ℹ️Kit/Bundle products: Kit and bundle products are generally supported by Product Sync. They are created and updated in Logiwa the same way as standard products. Kit component resolution against BOM rules applies specifically at the Order Fulfillment stage (below), not during Product Sync itself.


Inventory Sync (Logiwa to QBO)

Cadence & Trigger: Scheduled automation running every 10 minutes.

Calculation Logic: Unidirectional synchronization for inventory changes (such as shrinkage and cycle counts) finalized in Logiwa. Items must exist in QBO as an Inventory Item prior to adjustment posting.

Source Field (Logiwa)

Target Field (QBO)

Logic / Notes

SKU

Item Name/Number

Must match QuickBooks Online Item Name/Number exactly.

Quantity Change (+/-)

Quantity

The specific adjustment quantity being synced.

Date

Date

The date of the inventory adjustment.

Reason Code

Adjustment Account

Mapped 1:1 to a single QBO Account (Inventory Shrinkage).

ℹ️Kit/Bundle products: Kit and bundle SKUs are generally supported by Inventory Sync in the same way as standard SKUs.

⚠️Adjustment code and item type requirements: Shrinkage adjustments are sent to QBO using the Inventory Shrinkage Adjustment Code. QBO items must be listed as an Inventory Item. If an item is not listed as an Inventory Item in QBO, QBO will reject the Sync Inventory request for that item.


Purchase Order Sync (QBO to Logiwa)

Cadence & Trigger: Scheduled automation running every 10 minutes.

Business Rules: Checks QBO for newly created or updated Purchase Orders with status “Open”. Automatically creates Vendor profiles in Logiwa if missing, using QBO address data.

Source Field (QBO)

Target Field (Logiwa)

Logic / Notes

Vendor Name

Vendor

Finds or automatically creates a Vendor profile in Logiwa.

PO Create Date

PO Date

The creation date of the Purchase Order.

PO Number / ID

Custom Field (Text Box 3)

Unique QBO ID stored in Logiwa for reference and tracking.

Item Name/Number

Line Item SKU

Matched to Logiwa SKU formats.

Quantity

Pack Quantity

The total expected receiving quantity.

Purchase Order Fulfillment / Receiving (Logiwa to QBO)

Cadence & Trigger: Scheduled automation running every 10 minutes.

Business Rules: Checks Logiwa for newly processed receiving history records once items physically arrive at the warehouse.

  • Standard purchase receiving: Generates a Vendor Bill in QBO.

  • Customer-related receiving (e.g., return): Generates a Sales Invoice in QBO.

  • Prevents duplicate posts by flagging synced records.

Source Field (Logiwa)

Target Field (QBO)

Logic / Notes

PO Code

Invoice No / Bill No (DocNumber)

Mapped for both Invoices and Bills as transaction reference.

Customer / Vendor

Customer / Vendor (CustomerRef / VendorRef)

Matches corresponding profile in QuickBooks Online.

Customer Email

Bill Email (BillEmail)

Applies to Invoices; mapped for billing communications.

Billing Address

Billing Address (BillAddr)

Applies to Invoices; mapped from customer address details.

Line Item SKU

Item Name/Number

Matches physical SKUs against the QBO catalog items.

Received Quantity

Quantity

Actual physically received quantity in the warehouse.


Order Fulfillment (Logiwa to QBO)

Cadence & Trigger: Scheduled automation running every 10 minutes.

Business Rules: Checks Logiwa for shipment orders marked as “Shipped” or “Delivered”. Automatically resolves kit/bundle components into parent Kit SKUs using Logiwa BOM rules and embeds tracking details into invoice notes.

Source Field (Logiwa)

Target Field (QBO)

Logic / Notes

Original Order Code

Invoice No (DocNumber)

Links the QBO Invoice directly to the Logiwa Shipment Order. This is a distinct field from Channel Order Number (Order Sync). The two do not collide, and this flow does not create duplicate invoices against inbound Order Sync records.

Client Display Name

Customer (CustomerRef)

Matches QuickBooks Online Customer Company Name exactly.

Actual Shipment Date

Transaction Date / Ship Date (TxnDate / ShipDate)

Sets transaction and shipping dates on the invoice.

Carrier & Tracking No

Tracking Number & Private Note

Embedded in invoice notes for full tracking visibility.

Item SKU / Kit SKU

Item Name/Number

Matches individual SKUs or resolved parent Kit SKUs in QBO.

Shipped / Kit Quantity

Quantity

Actual shipped units, calculated via BOM for kit products.


Billing Sync (Logiwa to QBO)

Cadence & Trigger: Scheduled automation running every 15 minutes.

Business Rules: Checks Logiwa for user-approved billing calculations. Automatically creates invoices in QuickBooks Online without triggering automated customer emails.

Source Field (Logiwa)

Target Field (QBO)

Logic / Notes

Bill Number

Invoice No (DocNumber)

Logiwa Bill Number becomes the QBO Invoice Number.

Client Display Name

Customer (CustomerRef)

Looks up the QBO Customer ID based on Logiwa Client Name.

Fee Name

Product/Service (ItemRef)

Looks up the QBO Item ID based on Logiwa Fee Name.

Quantity

Quantity

The billable quantity of the specific line item.

Unit Price

Rate

The rate charged per unit.

⚠️Known limitation, Sales Tax & Payment Status: The integration does not calculate or sync Sales Tax on any invoice or bill, and payment status does not sync back to Logiwa in either direction.


Error Handling & Diagnostics

Error Type

Common Causes

System Behavior

API Connection Errors

Invalid OAuth credentials, expired access tokens, platform rate limits.

Automated retry triggers up to 3 times for temporary network drops.

Inbound Errors (QBO to Logiwa)

Missing data attributes, invalid data payload formats, unmapped product SKUs.

Record rejected and isolated while batch processing continues.

Outbound Errors (Logiwa to QBO)

Customer/Vendor name mismatch, missing required baseline fields, invalid field mappings.

Transaction update skipped and flagged.

Every system event captures the following diagnostic markers:

  • Timestamp

  • Target Endpoint

  • Transaction Status (Success/Fail)

  • HTTP Response Code

  • API Error Message

💡Processing logs aren’t accessible via the Logiwa dashboard. All troubleshooting inquiries must go through a support ticket via HubSpot.

Flow-Specific Error Scenarios

Flow

Example Error Scenario

System Behavior

Order Sync

Line Item SKU not found in Logiwa.

Record is rejected; other orders in the batch continue processing; error notification email is sent.

Product Sync

SKU field is missing or invalid.

Product is not created/updated; error is logged.

Inventory Sync

SKU does not exist in QBO.

Adjustment is not posted; “SKU Mismatch” notification email is sent.

Purchase Order Sync

Vendor name is missing or blank in QBO.

Vendor cannot be auto-created; PO is not processed; exception is logged.

PO Fulfillment / Receiving

Customer/Vendor name does not match across systems.

Transaction is not posted; “Entity Mismatch” notification email is sent.

Order Fulfillment

Kit BOM definition is missing or incorrect.

Kit line cannot be resolved; invoice is not created; exception is logged.

Billing Sync

Fee Name does not match a QBO Item.

Invoice line is not created; error notification email is sent.

Email Notification Reference

Automated error alerts are sent directly to your configured Contact Email:

Error Category

Notification Email Subject

Action Required

SKU Mismatch

[Logiwa QBO] Product Not Found

The SKU in QBO does not exist in Logiwa. Add the SKU to Logiwa or correct SKU alignment in QBO.

UOM Error

[Logiwa QBO] UOM Mismatch

The Unit of Measure string differs between systems (e.g., EA vs ea). Update UOM strings to match exactly.

Token Expired

[Logiwa QBO] Connection Lost

OAuth authorization has expired. Go to Logiwa UI, Manage Configuration, and click Re-authorize.

Entity Mismatch

[Logiwa QBO] Vendor/Customer Missing

Customer or Vendor display name does not match across systems. Align profile display names exactly.

ℹ️When opening a support ticket, include: QuickBooks Online Store Name, time of the error, QBO document number (if applicable), the error email’s subject line, and any error message shown in the email.


Common Questions & Edge Cases

Why did an order fail to sync from QBO?

Confirm the Line Item SKU exists in Logiwa, and that required customer/address data is present on the invoice.

Why isn’t my inventory adjustment showing up in QBO?

Confirm the SKU exists in QBO as an Inventory Item (not a non-inventory or service item), and that a Reason Code to Adjustment Account mapping exists for the adjustment type used.

Why did a Purchase Order fail to import?

Confirm the Vendor Name field is populated in QBO. Logiwa can auto-create a Vendor profile, but only if a name is present.

Why wasn’t an invoice created after I shipped an order?

Confirm the order is marked “Shipped” or “Delivered” in Logiwa, and, for kit items, confirm the Kit BOM definition is correctly configured.

Does this integration handle sales tax or payment status?

No. Sales Tax is not calculated or synced in either direction, and Payment Status (including partial payments and refunds) does not sync back to Logiwa. Both must be managed directly in QuickBooks Online.

Can I test this integration in a Sandbox environment first?

No. This integration only supports Production keys. Use clearly-labeled test customer/product names (e.g., “ZZ-TEST Customer”) during UAT, and delete or mark them Inactive in QBO once testing is complete.


Operational Best Practices

  • Maintain exact SKU alignment between QuickBooks Online and Logiwa before activating synchronization flows.

  • Maintain precise BOM definitions for bundled or kit items in Logiwa.

  • Verify entity display names. Ensure Customer and Vendor profile names in QBO match Logiwa display names exactly.

  • Manage administrative credentials. Keep the dedicated QBO admin user active and ensure OAuth 2.0 permissions are maintained.


Recommended Go-Live Test Checklist (UAT)

⚠️Since this integration only uses Production keys, these steps run against your live QBO company file. Use clearly-labeled test names (e.g., “ZZ-TEST Customer”) and remove/deactivate them in QBO once UAT is complete.

Test Order Sync

  1. In QBO, create a test customer and a test product.

  2. Create a test invoice for the test customer with 1 unit of the test product.

  3. Wait 10 minutes.

  4. Confirm the order appears in Logiwa with the correct customer, SKU, and quantity. Expected result: Order appears in Logiwa as a shipment order.

Test Order Fulfillment

  1. In Logiwa, complete the test shipment order (mark as Shipped).

  2. Wait 10 minutes.

  3. In QBO, confirm a Sales Invoice was created for the test customer with the correct SKU and quantity. Expected result: Sales Invoice appears in QBO automatically.

Test Inventory Sync

  1. In Logiwa, perform a manual inventory adjustment for the test SKU using a Reason Code mapped to a QBO Adjustment Account.

  2. Wait 10 minutes.

  3. In QBO, check the inventory adjustment transaction or the mapped account. Expected result: Inventory adjustment appears in QBO.

Test Purchase Order Sync

  1. In QBO, create a test Purchase Order with status Open.

  2. Wait 10 minutes.

  3. Confirm the PO appears in Logiwa under the correct vendor. Expected result: PO appears in Logiwa.

Test Product Sync

  1. In QBO, create or update a test product.

  2. Wait 15 minutes.

  3. Confirm the product appears in Logiwa with the correct SKU and price. Expected result: Product appears in Logiwa.

💡If any test fails, refer to the Email Notification Reference above. If the issue persists, open a support ticket with the details listed in that section.


Known Limitations

  • Sales Tax: Not calculated or synced by the integration; must be managed directly in QuickBooks Online.

  • Payment Status: Does not sync back to Logiwa in either direction, including partial payments and refunds.

  • Log Access: Currently not available via the Logiwa UI. All diagnostics require a support ticket through HubSpot.

Did this answer your question?