Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Dropship · Accounting
QuickBooks Online
DSCO (Rithum)
Connect QuickBooks Online + DSCO (Rithum)
Automate retailer order (accounting view), customer record, item mapping, credits and returns, deductions and allowances between QuickBooks Online and DSCO (Rithum) — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects QuickBooks Online and DSCO (Rithum).
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between QuickBooks Online and DSCO (Rithum), the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
For finance teams whose company runs retailer dropship programmes on DSCO and keeps the books in QuickBooks Online.
What needs to be in place
- QuickBooks Online with an authorised connection and a chart of accounts ready for retailer revenue.
- An active DSCO supplier account with retailer programmes onboarded.
- Clarity on which system holds order and inventory truth — QBO is not that system.
- A named finance owner to approve the mapping.
When you may not need this
A handful of retailer invoices a month can be entered manually. Integration matters when invoice volume grows, when deductions make revenue hard to explain, or when nobody can reconcile a retailer's remittance to your books.
What is out of scope
- QuickBooks Online is an accounting system. It is not an order-management or warehouse system, and we do not configure it as one.
- Retailer compliance, packaging and labelling stay operational responsibilities.
- Which QBO objects are written — invoice or sales receipt — is agreed in scoping with your finance owner.
What actually moves, and who owns it
A representative dropship accounting scope. Order execution deliberately sits outside QBO.
QuickBooks OnlineAPIWORX (mapping, retries, exception queue)DSCO (Rithum)
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Retailer order (accounting view) | DSCO | QuickBooks Online (invoice or sales receipt, as agreed) | Retailer (order) / QBO (ledger) | Order shipped or invoiced, per agreed rule | Held in exception queue; nothing posted partially | APIWORX |
| Customer record | Agreed rule | QuickBooks Online | QuickBooks Online | One customer per retailer programme | Held rather than creating duplicates | APIWORX (delivery) / you (rule) |
| Item mapping | Agreed mapping | QuickBooks Online | QuickBooks Online | Per line, where item-level posting is in scope | Unmapped SKU raises a named exception | APIWORX |
| Credits and returns | DSCO | QuickBooks Online | Retailer | Credit event received | Queued for finance review | APIWORX (delivery) / you (accounting rule) |
| Deductions and allowances | Retailer remittance | QuickBooks Online | Retailer | Remittance data available, where in scope | Unmatched amounts queued rather than plugged | APIWORX (delivery) / you (decision) |
| Shipment execution | Warehouse / 3PL | DSCO | Warehouse | Shipment recorded | Retailer rejections queued | APIWORX (data) / you (operations) |
Three decisions that make or break this integration
How retailer transactions become accounting records
Dropship revenue only reconciles if everyone agrees what triggers a ledger entry and what that entry looks like. That is a finance decision, taken before build.
- Trigger agreed — invoice on despatch, or on the retailer's acceptance.
- Object agreed — invoice where you carry a receivable, sales receipt where cash is effectively settled.
- One QBO customer per retailer programme, with the retailer PO number carried for lookup.
- Posting grain agreed: order level, or item level where SKU revenue reporting is needed.
Where order and inventory responsibilities sit
The most common QBO dropship failure is expecting accounting to run operations. Drawing the line explicitly keeps both sides working.
- The retailer owns demand; DSCO carries it.
- Your warehouse or 3PL owns fulfilment and shipment detail.
- QuickBooks Online owns customers, items, invoices and the ledger — nothing more.
- APIWORX owns the movement between them and the exception queue.
Reconciliation and exceptions
Retailer remittances rarely match invoices line for line. Making the difference visible instead of absorbing it is what keeps the ledger honest.
- Credits and returns posted against the original transaction.
- Deductions and allowances mapped to accounts your finance owner nominates, where remittance data is in scope.
- Unexplained differences queued for review rather than written off automatically.
- Every posted record carries the retailer PO and DSCO order reference so any query can be traced.
Reliability and ownership
Finance integrations earn trust by being auditable. These are the arrangements behind that.
- Every run is logged with the source record reference so a document can be traced end to end.
- Failed messages are retried on a defined schedule; anything that still fails lands in an exception queue rather than being dropped silently.
- Duplicate prevention keys on the source system's own identifier (order number, PO number, document ID) so a replayed message does not create a second record.
- Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
- Mapping changes — new SKUs, new accounts, new dimensions, new trading-partner requirements — are handled as part of the ongoing engagement.
- Response commitments and support windows are set in your agreement; this page does not state an SLA.
Illustrative posting map
Illustrative example — not a customer result
An anonymised mapping shape used to structure the finance workshop.
| Retailer PO number | QBO transaction → custom field / memo |
|---|---|
| DSCO order ID | QBO transaction reference |
| Retailer programme | QBO customer |
| Retailer SKU | QBO item (via mapping table), where item-level posting applies |
| Allowance / deduction | Nominated expense or contra-revenue account |
| Retailer credit | Credit memo against the original invoice |
Scope and questions
- Does this make QuickBooks Online our order-management system?
- No, and we would advise against trying. QBO holds the accounting record; order and inventory truth stay in the systems built for them.
- Invoice or sales receipt?
- It depends on whether you carry a receivable against the retailer. Your finance owner decides in scoping and we implement that consistently.
- Can you post at SKU level?
- Yes, where SKU revenue reporting matters. It requires an item mapping and adds reconciliation work, so we agree it deliberately.
- Are deductions handled?
- Where retailer remittance data is available and in scope, deductions are mapped to accounts you nominate. Unmatched amounts are queued for review, never plugged.
- What if we also sell direct?
- DTC revenue is normally kept separable from retailer programmes so margin reporting stays meaningful.
- How is scope determined?
- From the retailer programmes in play, the posting grain, remittance handling and the ongoing support you want.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your DSCO + QuickBooks Online integration
Tell us your systems and documents. A specialist confirms scope by email.