Getting help
How do I contact Junipeer support?
Email: support@junipeer.io
Phone: +46 (0)8 480 014 30
When contacting support about a sync issue, include the task ID or reference number from the Tasks or Logs page. This helps the support team investigate quickly.
Syncing and data
How do I check if my data has been synced?
Use the Tasks page to see whether a specific sync operation succeeded or failed. You can filter by entity type, status, and date range.
For a specific record (e.g., a particular order), go to the Entities page and search by reference number or ID. This shows the sync status and timestamp for that record.
The Logs page provides a more detailed view with error messages and warnings. You can filter by reference number to trace everything that happened for a specific record.
How do I search for a specific entity (order, customer, article)?
Go to the Entities page and select the entity type tab (Orders, Customers, Articles, Stock). Use the search/filter functionality to find the record by its ID or reference number. You can also view the raw JSON data for any synced entity.
Can I sync historical data from before the integration was set up?
Yes. Use the Time History page to move the "last loaded" date backward to the date you want to start from. This tells Junipeer to fetch records from that date onward on the next sync.
Start with a small date range (e.g., one week) to verify the results before backfilling a larger period. Keep in mind that the order exclusion date in Configure > Settings > Order Settings acts as a hard cutoff — records before that date are never synced regardless of Time History settings.
Why are some orders missing from the sync?
Orders can be missing for several reasons:
The order was created before the Time History "last loaded" date
The order falls before the order exclusion date set in Settings
A brief connectivity gap during a scheduled sync caused some orders to be skipped
The order does not meet filter criteria configured in Additional Filters
Check the Logs page first — if the order attempted to sync but failed, there will be an error entry. If there is no log entry at all, verify the Time History and exclusion date settings. You can manually trigger a sync for a specific order using Export One from the Flows page.
Invoices and payments
Can I edit a booked invoice?
No. Once an invoice is booked in most ERP systems, it becomes part of the accounting ledger and cannot be modified or deleted. This is a standard accounting principle, not a Junipeer limitation.
If a correction is needed on a booked invoice, you must create a credit note to reverse the original invoice (or a portion of it), and then create a new invoice if needed. Junipeer handles this automatically when a refund is issued in the e-commerce platform.
How does payment date priority work?
When recording a payment against an invoice, Junipeer may have multiple dates available. It uses the following priority order:
Payment provider date (highest priority) — the date the payment provider records the transaction
Order date — the date the order was placed in the e-commerce platform
Sync date (lowest priority) — the date Junipeer processed the record
This matters for payment reconciliation. If the payment date ends up before the invoice date in the ERP, you may see a "payment date cannot precede invoice date" error. See the Error Codes guide for resolution steps.
How does automatic transaction matching work?
When a payment provider settles transactions, Junipeer receives the payout report and matches each transaction to the corresponding invoice in your ERP using reference numbers created during order sync.
The matching is fully automatic — Junipeer uses the unique reference stored on each invoice to identify which payment belongs to which invoice. Once matched, the invoice is marked as paid and processing fees are booked to your configured fee account.
If a transaction cannot be matched (e.g., the invoice was created manually outside Junipeer and lacks the required reference), it will appear as unmatched in the logs.
Platforms and connectors
What types of connectors does Junipeer support?
Junipeer connects several categories of platforms:
E-commerce platforms — the source of orders, products, and customer data (e.g., webshop systems)
ERP / Accounting systems — the target for invoicing, bookkeeping, and financial data
Payment providers — the source of payout and settlement data for payment reconciliation
Data warehouses — for analytics and reporting (data flows out of Junipeer into your data warehouse)
Logistics providers — for shipping data and fulfillment status
For the full list of supported platforms and connector pairs, see the Knowledge Base homepage.
Can Junipeer build custom integrations?
Yes. If you need to connect platforms that are not in the standard catalog, Junipeer can build custom integrations. Contact support@junipeer.io to discuss your requirements.
What can be customized within a standard integration?
Standard integrations offer several customization options through Configure > Settings:
Field mappings between source and target systems
Shipping method and payment method mappings
Sales account and VAT rate mappings
Filter rules to include or exclude specific records
Default values for fields that may not exist in the source platform
Order exclusion dates and other sync boundaries
For customizations beyond what the settings interface supports, contact Junipeer support.
Multi-currency and cross-border
How does Junipeer handle multi-currency orders?
Junipeer passes the order currency from the e-commerce platform to the ERP. The ERP handles the actual currency conversion using its own exchange rates.
For this to work, all currencies used in your webshop must be enabled in the ERP. A missing currency will cause the order sync to fail. See the Bookkeeping guide for details on currency handling.
How does cross-border EU sales (OSS) work?
Under the EU One Stop Shop (OSS) regulation, you charge the VAT rate of the buyer's country for B2C cross-border sales. Junipeer supports this by reading the country-specific VAT rates from incoming orders and mapping them to the correct accounts in your ERP.
How this mapping works depends on your ERP — some require explicit per-country configuration in Junipeer, others handle it automatically through tax groups or built-in tax engines. See the Bookkeeping guide for a detailed explanation.
Billing and pricing
How does Junipeer pricing work?
Junipeer pricing is based on:
Per connector pair — each integration (e.g., Shopify–Fortnox) has a base fee
Per transaction volume — additional charges apply above 1,000 orders per month
Custom integration pricing is available for non-standard connector pairs. Contact support@junipeer.io for a quote.
How does billing work with multiple stores?
Each connector pair is billed separately. If you have three Shopify stores each connected to Fortnox, that counts as three integrations, each with its own base fee and transaction volume.
For troubleshooting common errors, see the Error Codes reference or your connector pair's troubleshooting section.