INTEGRATION · DEAR SYSTEMS
Dear Systems and Cin7 Core integrations live in production for retail, beauty, and B2B businesses. Real-time inventory parity, automated procurement, full audit trail.
Dear Systems was acquired by Cin7 and rebranded as Cin7 Core. It remains one of the strongest inventory and operations platforms in the Australian SMB to mid-market segment. If you are on Dear or have recently transitioned to Cin7 Core, you have a capable system at the centre of your operations. The platform choice is sound.
The challenge is what surrounds it. Dear/Cin7 connects to commerce platforms, accounting platforms, shipping platforms, and POS through a mix of native integrations and third-party connectors. The native integrations cover the common cases. The third-party connectors fill the gaps with variable quality. The system at the centre is strong; the connections that surround it are uneven.
The pain point we see most often: inventory parity. Stock counts on Shopify, on the website, on the POS, and in Dear/Cin7 should all agree. In practice, they drift. The drift causes oversells, customer complaints, and operational firefighting. The warehouse team learns to stop trusting the figures on the screen and check the shelves directly. That works until the volume gets too high.
The other common pain: accounting integration. Sales flow to Xero or MYOB, but the cost-of-goods side is incomplete or delayed. Inventory valuation reports do not match the accounting figures. Stocktake variance produces unexplained P&L movements. The CFO has stopped trusting the gross margin figure and reconstructs it from raw Dear exports each month.
Proper Dear/Cin7 integration solves both. Real-time inventory sync in both directions. Correct accounting flow for cost of goods, stock movements, and variance. Full audit trail.
The honest moment most agencies skip: most Dear/Cin7 stacks do not need custom middleware. If you are on a single warehouse, a single sales channel, and have inventory turnover that’s manageable manually, the native Dear-to-Shopify and Dear-to-Xero connectors are genuinely the right answer. We will tell you that directly. About one in four Dear/Cin7 discoveries we run ends with our recommendation to stay on the native connectors and just fix the underlying chart of accounts or procurement workflow. The middleware case starts at multi-warehouse, multi-channel, or where the volume has exceeded what the native connectors handle reliably.
If your Dear/Cin7 deployment is suffering from inventory drift or incomplete accounting flow, call 0431 000 062.
You probably need proper Dear/Cin7 integration when one or more of the following are true.
DIAGNOSTIC
If three or more describe your situation, the integration layer is the bottleneck. Proper middleware turns Dear/Cin7 from an island into a connected platform.
Every Dear/Cin7 integration on Nexus uses the same pattern. The components are deliberately boring. Boring is the point.
Both directions. When Dear/Cin7 records a stock movement, that event is captured. When a sales channel records a sale, that event is captured. Both flow through the same middleware. The middleware is the single source of truth for what happened and when, even though Dear/Cin7 remains the authoritative system for stock-on-hand.
Stock-on-hand is calculated as the authoritative number in Dear/Cin7. Sales channels are kept in sync through real-time push, not nightly batch. New stock receipts in Dear/Cin7 update sales channels immediately. The 11pm batch sync that used to break twice a quarter disappears entirely. Stock movements from sales push back to Dear/Cin7 within seconds.
Reorder rules in Dear/Cin7 trigger procurement events. Purchase orders, supplier ASNs, and goods receipts flow through the integration layer. Where suppliers have their own API or EDI connection, that connection lives in Nexus and stays out of Dear/Cin7’s way. The “manually email the supplier from Dear, then manually enter the ASN when it comes back” pattern disappears.
Sales generate revenue entries to Xero or MYOB. COGS entries follow on shipment or fulfilment, with correct inventory cost basis. Stock movements (transfers, adjustments, stocktake) produce correct accounting entries. The inventory valuation report in Dear/Cin7 now ties to the inventory balance sheet figure in the accounting system, without manual adjustment.
Orders ready for fulfilment generate ShipStation, StarShipIt, or equivalent shipping events. Tracking numbers flow back to Dear/Cin7 and to the sales channel. The customer’s tracking email comes from the commerce platform; the warehouse’s pick list comes from Dear/Cin7; both reference the same shipping event in the audit log.
For groups running multiple warehouses, Nexus handles the order routing logic. Each order is allocated to a warehouse based on stock availability, customer location, and configurable priority rules. The commerce platform shows pooled stock; the warehouse sees only its own allocations. The CFO sees the per-warehouse picture in the reporting layer.
Every event, every transformation, every write to every system is logged. Inventory variance investigation becomes a query. When the warehouse manager asks why a specific SKU showed stock-on-hand of 47 in Dear but 52 on the shelf, you trace it in the audit log within minutes. The “where did the missing five units go” question stops being a mystery and starts being a calculation.
We structure Dear/Cin7 integration engagements one of three ways. All three start with discovery.
Call 0431 000 062 to talk through which fits.
Three Dear/Cin7 integration projects. One named client, two confidential at client request. Reference calls available under NDA.
No account managers, no offshore teams, no juniors learning on your project. The two engineers below scope, build, and ship the work. The warehouse manager and the bookkeeper are both part of the discovery session. Dear/Cin7 sits at the intersection of operations and accounting, and both perspectives need to be in the room.
Nicolas Wendell
MANAGING DIRECTOR
Nicolas has been building custom software since leaving school, bringing a lifelong passion for development to every project. Before founding Paladine Systems, he ran his own video game studio and earned multiple accolades in network engineering. Known as a driving force in the custom software world, Nicolas combines deep technical expertise with visionary leadership – guiding Paladine in delivering innovative, enterprise-grade solutions.
Mark Morcom
SENIOR SYSTEMS ENGINEER
Mark is a young prodigy in software development, bringing 5 years of experience to Paladine. Equally at home on the front end and back end, he crafts clean, scalable solutions that power complex applications. Mark’s sharp problem-solving skills and passion for innovation make him a driving force behind Paladine’s most advanced projects.
Dear/Cin7 integration projects run in three phases. Each phase is fixed scope and fixed price.
DISCOVERY
2 to 3 weeks. Map current state, document warehouses, products, channels, accounting treatment, and procurement workflows. Produce a written scope and fixed quote.
BUILD
3 to 6 weeks. Stand up Nexus, integrate Dear/Cin7 and the surrounding systems, build the orchestration logic. Test against production-shaped data.
CUTOVER
1 to 2 weeks. Disable old connectors and batch jobs, turn on the new middleware, monitor inventory closely for the first weeks.
For most builds, total project time is 6 to 10 weeks. Multi-warehouse, Dear-to-Cin7 migration, or manufacturing module deployments run longer.
Yes. Cin7 acquired Dear Systems and rebranded the product as Cin7 Core. The platform is largely the same, though the API surface and the roadmap are evolving under Cin7 ownership. If you are currently on Dear, you do not need to migrate to Cin7 Core immediately; the Dear API continues to work.
Cin7 Omni is the legacy Cin7 product, distinct from what was Dear. We integrate with both, though the API patterns are different. If you have a mixed environment or are moving between them, we can scope the work. Most of our recent work is on Cin7 Core (the former Dear), but Omni deployments are supported.
We are Cin7 API integration specialists. We work with the official APIs of both Cin7 Core and Cin7 Omni. For platform-side implementation work (configuring Cin7 itself, training users, setting up the chart of accounts mapping), Cin7 has implementation partners. The two roles are complementary.
The platform migration is typically handled by Cin7 or a Cin7 partner. What we do is rebuild the integration layer for the new platform, which is usually required regardless of who handles the migration itself. We can run our work in parallel with the platform migration so that cutover happens cleanly with no integration downtime.
Yes. The most common request. We turn off existing connectors, route through Nexus, validate against historical data, then go live. The new middleware runs in parallel with the old connectors for the first two weeks so any final variance can be investigated before fully decommissioning.
Yes. Multi-warehouse is one of the main reasons businesses move from off-the-shelf connectors to custom middleware. The middleware handles stock pooling, order routing, and per-warehouse reporting correctly. The commerce platform shows combined available stock; each warehouse sees only its own allocations; the CFO sees the per-warehouse picture in the reporting layer.
Yes. If you have a custom ERP, CRM, or operations system, we build a connector. Nexus does not care what the other side is, as long as it has an API or database we can write to. About a third of our Dear/Cin7 work involves at least one custom downstream system.
Supported. Manufacturing orders, bills of materials, and assembly transactions can all flow through the integration layer to the right downstream systems. The accounting treatment of work-in-progress, finished goods, and component consumption is handled correctly on the Xero or MYOB side.
GET STARTED
