AI Powered integration with expert operators

Supercycle and Cin7 Core

Integration Agency & Consultants

Rental inventory creates a unique accounting burden when assets move in circles rather than lines. At scale, manual stock adjustments in Cin7 Core to account for returns or deposit refunds become a primary source of reconciliation debt. When your team can no longer trust asset availability without a manual audit, the operating model is under pressure. We integrate Supercycle and Cin7 Core to automate inventory updates and ensure rental hire fees are correctly categorised against security deposits in the ledger.

Castore
Lounge
Oliver Bonas
Green People
Tatty Devine
Cult
Scoping operational boundaries and asset ownership

Before technical work begins, we diagnose the operational requirements for the Supercycle and Cin7 Core integration. This discovery phase examines the source of truth for asset availability, manual workarounds currently used for hire returns, and how deposit data flows into the financial records. We establish clear ownership boundaries across finance and operations to ensure data remains consistent during the month-end close. The integration design, including data mapping and sync frequency, is finalised during this phase. This process avoids the risk of incorrect stock valuation and ensures that rental income is correctly categorised. By aligning the operating model before the build, we prevent reconciliation issues that typically arise from circular inventory movements and complex hire transactions.

Solution Design

For the Supercycle and Cin7 Core integration, we treat Supercycle as the authority for rental schedules and deposit logic, while Cin7 Core remains the source of truth for asset availability and financial valuation. A core design choice involves the categorisation of hire fees versus security deposits during the sync. We map these as specialised sales orders or stock movements to prevent rental income from being obscured by temporary deposit holdings. One significant trade-off is batching deposit refunds. While real-time updates provide immediate ledger activity, batching typically simplifies bank reconciliation and reduces the risk of manual month-end corrections. This design ensures the finance team can close books against accurate asset valuations, while the operations team manages rental stock based on confirmed return schedules rather than estimated availability.

Configuring inventory masters and rental logic

The integration establishes Cin7 Core as the authoritative inventory master while Supercycle handles the specialised rental logic. When a hire order is processed, the system triggers a stock update in Cin7 Core to transition the asset from Available to On-Rent. Upon return, the integration intake resets the stock status and handles deposit releases. Data integrity is maintained by ensuring SKU parity and mapping hire orders to specific Cin7 Core warehouse locations. We implement monitoring to detect timing gaps or status mismatches before they compound into inflated stock valuations or incorrect financial reporting.

Orchestrating data flows and retry logic

A controlled integration layer governs the data flow between Supercycle and Cin7 Core, managing critical movements such as asset status updates, rental orders, and return processing. This layer monitors for failure scenarios like SKU mismatches or malformed payloads that could lead to incorrect stock valuations. When a sync issue occurs, the layer applies business-rule validation at the boundary and follows a defined retry schedule with full payload logging. Threshold-based alerting ensures the operations team can intervene before stock drift affects asset availability. Supported by ISO 27001 and SOC 2 security standards, this infrastructure is managed by Cogent consultants and monitoring agents to ensure data integrity. This active oversight prevents the manual reconciliation delays often caused by circular inventory movements and return processing errors.

Monitoring stock status and deposit integrity

Dashboards confirm that data is moving, but they rarely surface whether it is moving correctly. We provide visibility into the specific state of your rental assets, flagging instances where a return in Supercycle has failed to update the availability in Cin7 Core. Hidden issues, such as hire fees being incorrectly logged as standard sales or VAT being applied to security deposits, are surfaced through exception reporting before they reach the finance team at month-end. By monitoring these operational triggers daily, we ensure the business can trust that the on-hand stock reported in Cin7 Core reflects actual asset availability rather than a legacy sync error.

Handover of circular inventory operating models

Training is built for the finance and operations teams who manage the Supercycle and Cin7 Core interface. We hand over a clear operating model that defines asset ownership and the specific routines for managing circular inventory movements. Your team learns what to check daily, such as sync status for returned rentals, and how to resolve exceptions like deposit reconciliation gaps or stock drift. Documentation is delivered as a practical operational reference for those running the business, not a technical archive for IT. This ensures the team can maintain a clean master inventory balance and accurate VAT treatment on hire fees as rental volume scales, reducing the need for external technical support.

Post-live governance and stock drift management

Ongoing support ensures your Supercycle and Cin7 Core integration adapts as your rental volumes and SKU count increase. We provide monitoring that surfaces sync failures or stock drift before they impact your warehouse operations. When exceptions occur, our team provides clear escalation and resolution steps, focusing on maintaining the integrity of your master inventory balance. We take operational ownership of the integration layer, managing the technical behaviour so your finance and ops teams can focus on fulfilment and reconciliation rather than troubleshooting. Support is provided on an agreed schedule tailored to your operational needs.

Integration operating model

In this model, Supercycle manages the rental logic, including return windows and deposit captures, while Cin7 Core acts as the master record for inventory and financial value. Every time a hire order is placed, the integration creates a specialised sale or stock movement in Cin7 Core, moving the asset from an available location to an On-Rent status. Returns follow the reverse path, with intake processing in Supercycle triggering a restock event in Cin7 Core. This ensures that the warehouse team works from a single source of truth for stock levels, and the finance team can report on hire income and deposit liabilities without manually stripping apart order data.

Common failures

Mismatched circular and linear returns.

Operational impact: A rental return processed as a standard sales return inflates stock-on-hand valuations and available-to-sell inventory. This requires the finance team to manually correct journal entries to avoid distorting gross margins. It also means VAT may be incorrectly calculated on what was a hire fee, creating compliance risks and rework during financial audits.

Prevention / Action: The integration logic must differentiate return types using a custom field on the return authorisation object sent from Supercycle. A rental return should trigger a stock adjustment or transfer between virtual locations in Cin7 Core, not a standard Credit Note that restocks an item for sale. This requires defining Supercycle as the source-of-truth for return reasons, with Cin7 Core configured to act on these specific instructions.

Incorrect General Ledger posting for rental fees.

Operational impact: When rental revenue and refundable security deposits are not properly segregated, they can be posted to the same account. This misrepresents turnover in management accounts and makes daily financial reconciliation a painful manual process for the finance team. At month-end close, unpicking these commingled journal entries can compromise the integrity of the financial statements.

Prevention / Action: The integration should use distinct, non-stock service SKUs to represent rental fees and deposits on the Sales Order. These unique SKUs must be mapped to separate General Ledger accounts within Cin7 Core's integration settings. This ensures that when a Supercycle order syncs, Cin7 Core automatically posts the debits and credits to the correct revenue and liability accounts.

SKU duplication for rental vs. purchasable stock.

Operational impact: Creating separate SKUs for the same physical item (e.g., 'ITEM-A-NEW' and 'ITEM-A-RENT') doubles SKU management overhead and splits the item's inventory history. It prevents a single view of asset value and can lead to the fulfilment team accidentally shipping a 'new' item for a rental order. This complicates stocktakes and makes accurate inventory valuation almost impossible.

Prevention / Action: A single master SKU should exist in Cin7 Core for each physical product. The item's condition or availability for rental versus sale should be managed by moving stock between different virtual 'warehouses' or 'locations' within Cin7 Core. The integration logic from Supercycle must then correctly update the stock location for the specific item, preserving a unified view of the asset.

Inventory latency and overselling of unique assets.

Operational impact: Delays in syncing Supercycle rental confirmations back to Cin7 Core mean a unique asset can be booked twice. This immediately creates a fulfilment crisis and a poor customer experience. The CX team has to manage the disappointed customer, while the operations team must find an alternative, which may not exist for specialised rental stock.

Prevention / Action: An event-driven integration trigger should be used to lock the inventory item in Cin7 Core the moment a rental is confirmed in Supercycle. This is more resilient than a batch-scheduled sync that runs every few minutes. The integration design should prioritise this 'asset allocation' message, treating it as a higher-priority task than other data syncs to minimise the window for overselling.

Frequently asked questions

Which system is the source of truth for inventory? Supercycle or Cin7 Core?

Cin7 Core remains the single source of truth for all inventory quantities and valuations. Supercycle manages the rental transaction logic in Shopify, but the integration ensures every rental order or return creates a corresponding stock movement in Cin7 Core. This keeps the master item record in Cin7 Core accurate, preventing you from renting out assets that are not physically available.

How does the integration handle rental returns? Won't they be treated as standard sales returns in Cin7 Core?

This is a common failure point that a specialised integration prevents. When Supercycle processes a rental return in Shopify, it triggers a unique stock adjustment in Cin7 Core, not a standard sales credit or restock. This ensures the item's status is correctly updated (e.g., from 'On-Rent' to 'Available') without incorrectly inflating your stock valuation or creating false credit notes.

How do we stop rental fees and security deposits from being mixed up in our Cin7 Core accounts?

The integration uses Supercycle's data to distinguish between different transaction types within a single Shopify order. A rental order from Shopify can create a sales order in Cin7 Core that uses separate non-stock lines for rental fees versus the refundable deposit. This ensures your financial reporting in Cin7 Core is clean from day one, avoiding a manual unpicking of revenue from deposits during your month-end close.

We are scaling our rental service. Can the integration automate deposit refunds in Cin7 Core?

Yes, this is a key process to automate as rental volume grows. When a deposit is refunded via Supercycle and Shopify, the integration can automatically generate the corresponding Credit Note in Cin7 Core against the original sales order. This removes the need for the finance team to manually create these credit notes, which is a common source of error and delay in the returns handling process.

Get Started

We would love to hear about your brand and project