This guide is for anyone connecting Specter to another system through Junipeer — a webshop such as Shopify, WooCommerce, Geins, Norce or Magento, the shipping service Sendify, or the payment provider Qliro. It explains what the integrations do, how to connect Specter, and the main setting areas.
The exact flows and settings depend on the pair you use. The titles below are the ones the app shows; click the ? next to a setting for details.
What Specter integrations do
Specter is usually the system where orders are handled and stock is kept. The flows available depend on the other system:
Paired with | Typical flows |
|---|---|
Shopify | Export Orders to Specter, Export Products to Shopify, Export Products to Specter, Export Stocks to Shopify, Export Shipment to Shopify, Update Order Statuses in Shopify, Export Customers to Shopify, Export Payouts to Specter |
WooCommerce | Orders to Specter; products, customers, order statuses and shipment tracking to WooCommerce |
Geins | Orders to Specter; products and stock to Geins; order status (and tracking number) back to Geins |
Norce | Orders to Specter; products, stock, shipments and customers to Norce |
Sendify | Send Orders to Sendify, Send Shipments to Sendify |
Qliro | Credit invoices from Specter to Qliro — see Qliro ↔ Specter |
Turn on only the flows you need under Get Started → Select flows.
Connecting Specter
Specter is connected with three values from your Specter account:
Specter Api User ID
Specter Sbm Id
Specter Api User Key — stored as a secret. Keep it private.
The connection settings also hold:
Specter PLUS Api Keys and Specter Payment Api Keys — separate sets of the same three values (API user ID, SBM ID, API user key). Leave them empty unless your setup uses them.
Currencies (key, title) — the currencies you use in Specter, for example SEK and Swedish krona. They then appear in other settings.
Discount Price Lists (Rabattprislistor) — your Specter price lists, so they can be chosen in Pricelist used for special price.
After changing these lists, click Clear Cache on the settings page so the lists are refreshed.
Separate API users per flow
Map Specter Api Keys with flows is needed when you want to load both invoiced orders and shipped orders from Specter, but in different flows. For each flow you add, Specter API User Id and Specter API User Key are required.
Orders sent to Specter
These settings control how webshop orders look in Specter:
WebshopId for the order — if several webshops are linked to Specter, the webshop ID orders come from, so documents get the right logo. Leave it empty if you have one webshop. Use Map WebshopId for different IDs per shop or market.
Default (Shipping fee) Article number. — the article number for the shipping row. If empty, frakt is used. It is also used to recognise the shipping row on orders loaded from Specter.
Always send shipping row — default No. Yes adds a shipping row even when shipping is free.
Default Discount Article number. — used for discounts on the whole order. If empty, rabatt is used.
Discount Percentage — by default both the price and the discount percentage are set on each row. Use this to send the discounted price instead.
Shipping methods — by default the shipping method is identified by its code. Map codes in Map Shipping methods (by CODE), or set Match Shipping methods by Name to Yes and use Map Shipping methods (by NAME). You find the external delivery methods in Specter under Inställningar → Leveranssätt.
Map Shipping methods in Order Rows — only if different shipping methods need different shipping articles.
Set NotifyDeliveryByMobile to 1 (set delivery notification via SMS) — requires SMS/Brevavisering set to enligt order in Specter.
Exclude Orders created before this date — on the webshop side, keeps old orders from being sent on the first run.
Mapped values must be typed exactly as the webshop sends them, with the same spelling and upper/lower case. A value that doesn't match is skipped without an error.
Orders loaded from Specter
Flows that read orders from Specter (order statuses, shipments, Sendify) use:
Managed Orders statuses — which status an order must have in Specter to be picked up. The default is Skickas and Avslutad.
Exclude Orders created before this date — orders created in Specter before this date are not synced.
Payments and pay types
Map Payment methods — connects each webshop payment method with a Specter pay type, a 2-character code, for example Klarna (K) or Swish (SW).
Payment Method Settings — extra settings per payment method:
Payment Method (required) — the Specter pay type.
Payment Reference Field (required) — Payment Reference (default) or Order Number.
Pay Type System User — only in rare cases, for example several Svea merchant accounts in Specter. Then enter the Svea merchant number.
Map Webshop to Pay Type System User — a different pay type system user per webshop.
For payouts sent to Specter:
Payout Reference Number — which reference finds the order in Specter: Order ID (default) or Payment ID.
Add Payment Reference Prefix — for example SHOP- turns reference 1001 into SHOP-1001. Leave empty if you don't need it.
Products and variants
Default Currency Code (required) — SEK if not set.
Sync ViewInShop Articles only (required) — Yes exports only articles marked Visa artikeln i shop. With several webshops, limit it with Specific WebshopIds for ViewInShop Articles (for example 1,2,7).
Pricelist used for special price — only one special price can be exported.
Add Variant Types and Map the variant values with suffixes — must match the variant definitions in Specter.
Force Article Update — when products go to Specter. By default Specter does not update articles that already exist.
Stock
Default Specter Warehouse ID (required) — default 1.
Load stock changes from all Warehouses — default No. Turn it on if you use several warehouses, or one that isn't the main warehouse (Huvudlager).
Shipments and tracking
Product Numbers to ignore — SKUs left out when shipments are loaded from Specter, for example a shipping or fee article.
WooCommerce: Shipment tracking provider and Shipment tracking link need the WooCommerce Shipment Tracking extension.
Geins: Set tracking number (if available) sends the tracking number of shipped orders.
Notes per pair
Sendify — fill in a sender under Senders (name, address, contact phone and e-mail). Require Packages and Enable Bookable Validation are required. If Default Sender is empty, the team's home address is used.
Qliro — Qliro must be its own payment method in Specter, and crediting needs Qliro API Plus credentials. See Qliro ↔ Specter.
Geins — product import needs answers to Create new products, Update products, Update prices, Disable new products in Geins, Default Market Id, Map article to multiple markets and Geins Non Stock type.
WooCommerce — connect with WooCommerce Shop Url, WooCommerce Consumer Key and WooCommerce Consumer Secret (created under WooCommerce → Settings → Advanced → Rest API).
Norce — connect with Norce Client name, Client ID, Client Secret and Default application ID.
Cancelling orders in Specter
Cancel with the red box in Specter, not the trash can. Specter does not tell Junipeer about deleted orders, so a deleted order stays open in the connected payment provider. See Cancelling orders in Specter.
Test, then schedule
Test one order before scheduling: use Export One on the Flows page, check Tasks and Logs, and look at the result in Specter yourself. Then add schedules under Get Started → Start Syncing.