Agreement
Terms of use
These terms apply to business access to and use of Linkivo unless otherwise agreed in writing.
Invited users
An administrator can invite a user to an existing customer account by email. The invitation is valid for 24 hours and can be accepted once. A replacement invitation invalidates the previous pending link. The recipient chooses their own password and completes normal login with an email one-time code. An invitation does not buy a subscription or enable integrations. The administrator is responsible for selecting the correct customer and recipient.
1. Parties and scope
Linkivo is provided by CT-IT ApS, CVR 45578267 (“Linkivo”, “we” or “us”). The customer is the business creating or receiving access to a Linkivo account. The service is for business use and is not intended for consumers.
A separate order, proposal, data processing agreement or service-level agreement prevails if it conflicts with these terms.
2. The service
Online signup currently offers Shopify + Rackbeat. Combinations with e-conomic require a separate setup agreement and are not available for online purchase. The selected combination determines connections and one permitted route for each data area. Shopify supplies sales; Rackbeat, when selected, controls warehouse data and supplies invoice data to e-conomic. With all three systems, sales do not also take the direct Shopify-to-e-conomic route. Transfers remain disabled until connections and settings are approved. Functionality depends on configuration, third-party APIs and permissions.
Where separately agreed, direct Shopify-to-e-conomic transfers create drafts from paid sales using one configured base currency, sales country and VAT rate. Discounts and shipping are checked against totals. Changed, cancelled or refunded sales, gift cards, duties, mixed VAT and currency differences require reconciliation. There is no automatic posting, payment, inventory valuation posting or bill-of-materials calculation. Runs are manual or scheduled; immediate real-time synchronisation is not promised.
Existing assisted agreements may additionally include selected reverse flows, supplier data, contacts, delivery addresses, currency prices, price agreements and separately stored Linkivo supplements for editing, import and export. These features depend on the agreed configuration and vendor API support.
When explicitly enabled, configurable Shopify-to-Rackbeat order workflows may match or create customers, preserve purchase addresses and sold line names, and confirm orders with or without a pick list or create invoices. Order numbering can use Rackbeat’s number series or an explicitly selected numeric Shopify order number. Number conflicts stop the transfer; existing orders are not renumbered. An optional customer policy creates a separate Rackbeat customer card per Shopify order, numbered from the order within a selected limit of up to nine digits. Repeated email addresses do not merge these cards. Existing cards and historical documents are preserved; unknown creation results require reconciliation without automatic repetition. Invoice posting requires a separate setting. These actions do not send customer email or mark goods as shipped. Uncertain provider responses stop automatic repetition and require reconciliation. Document texts can be configured for new order plans. Rackbeat’s employee reference may be kept, cleared or selected from existing reference cards. Linkivo retains durable document ownership independently of the visible reference. An unprovable write result requires manual reconciliation without automatic recreation. Historical documents are not changed. An authorised operator may correct a sold line name for a specific order before transfer, with a language, reason and dry run. The correction is recorded in configuration history; it does not change the source order or item master names. The customer must approve country, tax, customer-group and payment rules before activation.
The customer can select the current Shopify product translation as a fallback when a saved sale name in the order language is missing. It may differ from the name at purchase. The source and any selected market are shown in the plan; names and amounts are frozen before transfer. The customer must verify the shop’s primary language and any market-specific translations. A missing suitable translation stops the order for review. Changing the fallback does not rewrite transferred documents.
Inventory transfers support up to ten unique pairs of active Rackbeat and Shopify locations. Each location can belong to only one pair. Quantities are not combined; configured safety stock is deducted for each pair. Unselected Shopify locations are unchanged. Without pairs, exactly one active Shopify location is required. Missing or barred locations stop inventory transfers until the customer corrects the links. The customer must check location pairs and quantities before activation.
Optional market-context matching may keep separate customer links for different customer groups, tax zones, currencies and languages. It does not overwrite existing customer master data. Inventory transfers can be limited to an explicit list of Rackbeat item numbers; every webshop variant requires a verified link and an unambiguous location. Saving these links does not activate inventory transfers. Return review items distinguish money from stock-return instructions; approving or reviewing such an item is not an automatic credit note, payment or physical stock receipt. Tracking requires an agreed source supported by the provider.
When event rules are enabled, customers can store item groups, amount bases, comparison currencies, payment methods and order states. Unsaved rules require a dry run before saving; dry runs do not change connected systems. A completed refund can create a credit draft or posted credit note when separately selected. Stock returns require an independent choice, a completed refund, a location and evidence of the original shipment and cost price. Automatic stock returns currently support Rackbeat average cost only, when the current cost matches the original shipment. FIFO, changed cost or an unverifiable movement value require manual reconciliation. A return request alone is not proof of a refund or physical receipt. Invoice events can add text in a dedicated Linkivo field on the Shopify order without overwriting staff notes when a documented original order is available; Shopify timeline comments are not supported by the API. Applied exchange rates and timestamps are retained with rule results. Customers must clarify amount thresholds and mixed item-group handling. Provider permissions, currency data and original document links may limit available actions.
Optional inventory alerts periodically read a selected Rackbeat item group and location, using physical or available quantity as explicitly selected. The first observation establishes a baseline without alerts. A transition from positive quantity to zero or below queues one notification per depletion cycle; positive stock rearms the rule. The service polls and does not guarantee immediate alerts or observation of changes between polls. SMTP retries can duplicate delivery. The customer selects and authorises recipients. Alerts do not change stock, item groups or purchase orders.
Customers may request features. Linkivo may develop small, reusable additions without a separate development fee where they fit the product direction and can become part of the standard product. Linkivo decides eligibility and agrees scope, priority and expected delivery in writing. Customer-specific projects, new integrations and work outside the standard product are excluded.
Closing order monitoring
Authorised users may close monitoring of a specific permanent failure with a reason when the order write is confirmed and no writes are unresolved. The order is then skipped in subsequent runs without repeated failure notifications. This is not approval or accounting reconciliation. The original failure, duplicate protection and decision history with actor and time remain under the existing workflow retention rules. The customer remains responsible for reconciliation in connected systems and may explicitly reopen monitoring. No order, invoice or shipment is changed by this choice.
Rackbeat discount group synchronisation
Discount group synchronisation is optional and requires an administrator to review the account scope and expressly approve activation. Linkivo reads customer discount fields and uses them to maintain its own Rackbeat discount groups, customer overrides and product assignments within the approved scope. Activation requires the administrator to approve product groups whose Linkivo discount field is linked after activation. Linkivo automatically includes those groups once the field is verified. An empty discount field removes the corresponding verified Linkivo customer relation. A product assignment conflict is shown for review. The affected product is left untouched while other products and customer rates continue syncing. An agreement administrator can expressly approve replacing the product’s current discount group with the expected Linkivo group, or exclude the product and keep its Rackbeat assignment. Linkivo rechecks an excluded product when its product group or discount group changes. An agreement administrator can also explicitly resume the assignment. The customer must review general discounts, customer group discounts, special prices and quantity discounts. Setup does not audit quantity discounts. Rackbeat applies the saved rules when it prices new order lines. Prices may lag behind changes while synchronisation or reconciliation is pending, and the customer must check prices before confirming an order.
Linkivo does not edit existing order lines through this feature. Concurrent edits in Rackbeat may occur between validation and a write. Uncertain writes and conflicts require reconciliation. Pausing the service stops new synchronisation and leaves existing rules in Rackbeat in effect. Removal of owned settings is a separate operation requiring confirmation. Ownership, consent and write receipts follow the account’s operational-data retention. One run counts when a customer rate change is verified in a group that was already ready. Changes handled together for one customer count once, including retries. Initial rates at activation or for new groups, unchanged checks, unsuccessful attempts and product assignments do not count. If capacity is exhausted or the subscription is inactive, Linkivo skips the rate change and shows the reason. Previously saved rates remain in effect until another sync succeeds. The customer remains responsible for reviewing the resulting price in Rackbeat.
Order-total rounding
Optional gross-total rounding in Shopify-to-Rackbeat order workflows is disabled by default. After explicit accounting approval, a separate non-stock item with 0% VAT may add at most one positive minor currency unit to a new unposted draft when line-versus-document tax rounding is verified. A separate opt-in can include mathematically verified extraction of VAT from tax-inclusive line totals. An additional opt-in, requiring renewed accounting approval and a dry run, checks all such lines together and permits a total adjustment of at most one minor currency unit in either direction. No adjustment line is added when the differences cancel. Existing positive-only approvals retain their original limits. The option for both directions also covers an exact split of the net amount of a line across two unit prices when its original quantity, amounts and inclusive VAT are verified and retained as evidence. The split preserves quantity and net amount; VAT rates and source amounts are unchanged. Rackbeat net and VAT may differ from Shopify while the gross total matches exactly. The customer must approve the item, account and tax treatment with their accounting adviser. Larger or unproven differences, mixed VAT rates, historical documents and locked documents are not automatically corrected. A separate source-allocation option permits a configured correction of up to five minor units in either direction in supported two-decimal currencies after renewed accounting approval. A currency-specific opt-in may set separate limits for the document correction and each source-line VAT difference, each capped at 500 minor units (5.00 in the selected currency). It requires renewed accounting approval and a dry run; other currencies retain their existing limits. The complete source totals must reconcile and one VAT rate must apply. It preserves Shopify gross while accepting bounded differences in net and VAT. A new unposted draft is checked before and after one correction attempt; a successful correction is recorded without a failure notification. Unresolved corrections and larger differences follow normal failure notification rules. Refunds of rounding lines require manual reconciliation. Uncertain writes are not blindly repeated; approval and transfer receipts follow the existing order-workflow retention.
3. Account and access
An administrator may assign multiple customer accounts to one user. The dashboard account selector only provides access to explicitly assigned accounts. Settings, connections, subscriptions and support access are checked separately for the selected account. Removed access takes effect on the next server request.
Onboarding is an application and does not itself create an active account. Email must be confirmed by a one-time code, and activation requires a signed Stripe event confirming the required subscription. If paid setup is interrupted, Linkivo retains the conversion receipt and reuses the same customer and login when setup resumes. Use the same login details; do not pay again. Normal customer login requires a one-time code after the correct password. For configured system administrator accounts, an approved one-time code may be remembered in the same browser for 24 hours from approval; new logins still require the correct password. This approval is not extended by activity and is invalidated by explicit logout or changed credentials. Dashboard sessions still expire after 30 minutes of inactivity.
The customer must keep user data accurate, restrict access to authorised persons and protect credentials. We may temporarily restrict access for suspected abuse, security incidents, non-payment or material breach.
4. Customer systems and responsibilities
The customer must be authorised to connect Shopify, RackBeat, e-conomic and other systems and to process the selected data. The customer must maintain required subscriptions, API access, correct SKUs and responsible master-data rules. The customer may select categories for ordinary warning emails. Approvals and failed runs are notified separately. The customer must continue to monitor the dashboard and run logs when warning categories are disabled, and is responsible for authorised operational email recipients and removing obsolete addresses.
Before an e-conomic transfer, the customer must check group and payment-term mappings, VAT, currency, existing records and dates, and disable overlapping flows in other integrations. A preview reads and validates data without changing the external systems; only an actual transfer can confirm write permissions. Financial drafts must be checked in the accounting system before posting. Ambiguous API outcomes require reconciliation before automatic creation can resume.
Where configured, Linkivo may create technical master data, cancel linked orders or create and update Shopify products, variants, inventory links and collections. External systems may prevent cancellation of shipped, invoiced or locked orders. The customer must verify groups, tax, payment, inventory, product and publication rules, review the first synchronisation and follow up on errors and manual decisions.
Optional field rules can translate, combine, replace or clear supported values. Where an administrator enables customer rules from RackBeat to Shopify, these rules may update customer profiles, addresses, tags and metafields and, if separately enabled, create customers. The customer must check rule outputs, matching and ownership of fields before activation. Saving field rules does not itself activate customer synchronisation. Enabled order rules may update delivery dates on existing RackBeat orders using matched Shopify orders when the integration and webhook automation are active, even if order import is disabled. These rules do not create orders.
Where separately enabled by an administrator, RackBeat field setup creates account-wide customer discount dropdowns from product groups. Automatic field creation is a separate opt-in, disabled by default, that periodically includes existing and new groups. It is controlled independently of other integration pauses and does not apply discounts to orders. Conflicts and uncertain creations require review; disabling retains fields, customer values and write receipts.
Linkivo may not be used unlawfully, for unauthorised access, harmful code or infringement of third-party rights.
Cost price synchronisation
Optional cost synchronisation copies Rackbeat cost prices to existing linked Shopify inventory items, including multiple variants linked to the same source item. This flow does not create products or change sales prices, names, SKUs, status or stock quantities. The customer must declare the source currency, which must match the Shopify shop currency; no currency conversion is performed. Missing or conflicting mappings and invalid costs require correction. Customers can exclude exact item numbers and choose to skip blocked items. These choices are recorded in the run log without a cost update or error notification; other errors remain visible. Work is bounded per run; large initial selections may require multiple runs.
5. Personal data
The customer is generally controller for customer, order and employee data transferred through the integration. CT-IT ApS normally processes such data under the customer's documented instructions. Where required, the parties enter into a data processing agreement covering purposes, data types, deletion, security and subprocessors. Special-category personal data must not be sent unless separately agreed and lawful.
6. Subscription, prices and payment
For new subscriptions, the public Shopify + Rackbeat plans offer monthly capacity: up to 200 runs for DKK 299 and up to 1,000 runs for DKK 499. For more than 1,000 runs per month, contact us to agree pricing and capacity. Prices and scope for separately agreed integrations are agreed separately. Where multiple connections share an agreed subscription, each uses that shared capacity and a controlled system change preserves its billing identity. Prices are monthly, in DKK and exclude VAT. Existing subscriptions retain their agreed prices and capacity unless a change is separately agreed. Existing assisted agreements may have separate terms. Approved reusable requests under section 2 have no separate development fee; onboarding, customer-specific development, data cleansing and work outside the standard product may be charged separately.
A written introductory or campaign offer may change the first payment, including by making the first month free. The written offer states its scope and duration. After the offer period, the selected monthly plan is billed at its ordinary price until cancelled, unless otherwise agreed in writing.
Subscriptions are billed monthly in advance and renew until cancelled. Server-side Stripe prices determine product, price, currency and capacity. Stripe handles Checkout, card data, receipts and the billing portal. VAT is calculated from the billing address, country and tax identification number. Because Linkivo is offered to businesses, a supported tax identification number must be provided in Checkout where Stripe supports collection. Linkivo stores necessary Stripe references but not full card data.
Shared individual subscriptions
Where agreed in writing, one Stripe subscription may cover several explicitly selected customer accounts at one combined price. Payment status, cancellation and expiry apply to all accounts covered by that subscription. Capacity follows the written agreement. This billing link does not grant users access to other accounts; user permissions remain separate. Changes to the accounts covered or the agreed plan require assistance from Linkivo.
7. Plan limits and excess use
A run processes new or changed integration data, started by a webhook, schedule or authorised manual action. Related new Shopify–Rackbeat jobs for the same customer, connection and work class may share one visible run and capacity claim during a bounded admission period. All technical jobs, events and receipts are retained. A full manual request is not replaced by narrow work. Separate financial actions, connections and full inventory checks are not combined. Historical runs and usage are not recalculated. Rejected duplicates do not create a new run. Automatic technical retries and interrupted Shopify sales jobs reuse the original run; other independent manual runs count separately. Previews and empty direct Shopify sales checks do not count. A direct Shopify sales batch handles up to 50 sales; additional pages count as separate runs. A started transfer counts even if external data or systems later cause failure.
Usage is measured per Stripe billing period. At a fixed limit, new runs are rejected until renewal or upgrade. Inactive or unpaid subscriptions cannot start runs. Capacity above 1,000 runs per month is agreed separately. The service must not unreasonably burden Linkivo or third-party APIs. No unagreed overage fee is charged.
8. Operations, maintenance and support
We take reasonable steps to provide stable operations and remedy errors. Planned maintenance is placed outside normal business hours where practical. Continuous or error-free operation is not guaranteed unless a separate service-level agreement says otherwise. Changes at Shopify, RackBeat, Stripe or other suppliers may require adaptation or temporary limitation.
The dashboard support form requires a signed-in customer account with an active, paid subscription. Email remains available for account, payment and other enquiries. Support requests are handled in Linear and by email, and our staff may use AI assistance to investigate and respond under CT-IT ApS's responsibility; customers should include only information needed to resolve the request and must not submit passwords, API keys or unnecessary personal data. No fixed response or resolution time is promised unless separately agreed.
9. Data, logs and termination
SKU approvals retain a minimal receipt with the connected accounts, product identifiers, selected item, processing status and the deciding user and time. These receipts follow account retention and remain when ordinary approval history expires, to prevent conflicting or repeated updates. An unresolved write and its pending approval require reconciliation before processing or operational reset can continue; a timeout does not prove that Shopify was unchanged. Receipts contain no credentials or complete customer or order payloads.
Authorised users can permanently delete previous integration data in Settings, for a selected period or the entire history. Related product mappings, approvals and run logs may be included outside the period to keep the reset consistent. Configuration, credentials, users, subscriptions and recorded usage are retained. Financial profiles and retained accounting links require an assisted reset to preserve transfer receipts. This does not delete data in connected systems. Subsequent runs may import and process data again under the saved rules, including creating changes or duplicates; the customer must review rules and the order period before restarting.
Operational logs, operational mail queues, webhook-flow data and Stripe event receipts are normally stored for no more than seven days. Pending webhook work and unresolved run logs are retained until reconciliation. Release-write receipts contain only identifiers, state, request hashes and timestamps; no credentials or raw payloads. Approval decisions are normally stored for up to 30 days, and minimal run counts may be retained for up to 13 months. Other customer and accounting data is retained as described in the privacy policy and applicable agreements.
Completed order-workflow and address snapshots are removed from active history after seven days. Unresolved attempts retain the control data needed for reconciliation until the transfer is resolved. Minimal transfer receipts and customer links remain to prevent duplicates, including system identifiers, processing status and a hash of the matching email and, when selected, its market context. Event receipts also retain a hash of the original action plan, original rule decisions and the comparison amounts, exchange rates, sources and timestamps used to decide the rules. Resetting these links requires assisted reconciliation. Retention and deletion at termination follow the data processing agreement.
At termination, access ends and data is deleted or returned as agreed and required by law, documentation, security or the data processing agreement. The customer remains responsible for exporting required data from connected systems and from Linkivo supplements. Supplement exports do not update vendor fields or replace a legally required accounting archive.
10. Intellectual property and feedback
Linkivo and its standard product, source code, design, documentation and reusable additions belong to CT-IT ApS or its licensors. The customer receives a limited, non-exclusive right to use the service during the subscription. Customer data remains the customer's. Feedback may be used to improve the standard product without disclosing confidential information.
11. Confidentiality
Each party must protect non-public business, technical and security information and use it only to perform the agreement. Disclosure is permitted where required by law or to advisers and suppliers bound by appropriate confidentiality duties.
12. Liability
Each party is liable under Danish law subject to these terms. Linkivo is not liable for indirect loss, loss of profit, goodwill or expected savings, or loss caused by customer configuration, external systems, internet or APIs outside Linkivo's reasonable control. Unless caused by intent or gross negligence, Linkivo's aggregate liability is limited to fees paid for the affected product during the previous 12 months. Mandatory liability cannot be excluded.
13. Term and termination
The subscription runs until cancelled through Linkivo or Stripe's customer portal and remains active through the paid period unless otherwise agreed. Already paid amounts are generally non-refundable. A material breach may lead to termination after a reasonable written remedy period; serious security breaches or illegal use may result in immediate suspension.
14. Changes
We may update these terms when the product, law or supplier relationships change. Material changes are normally announced at least 30 days before taking effect. If a material change clearly disadvantages the customer, the customer may cancel before it takes effect.
15. Governing law and disputes
The agreement is governed by Danish law. The parties must first try to resolve disputes through dialogue. Otherwise disputes are decided by the Danish courts at CT-IT ApS' venue.
16. Contact
Questions about these terms may be sent to support@linkivo.dk.