✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Fortnox Integration: order & invoice sync as tables

Read directly from wc_orders and the Fortnox meta keys the integration stores. Surface invoice number, Fortnox customer number, and last sync status as real columns instead of per-order detective work.

♾️ Lifetime License available

SleekView table view for WooCommerce Fortnox Integration

Find failed Fortnox syncs without opening every order

WooCommerce Fortnox Integration plugins (the popular Scandinavian set, including the official Fortnox-branded integration and several community variants) push WooCommerce orders to Fortnox as invoices or orders, storing the Fortnox document number and customer number back in wc_orders_meta under keys such as _fortnox_invoice_number, _fortnox_customer_number, and _fortnox_sync_status. The default Orders screen shows none of this; failed syncs hide until a customer notices a missing invoice.

SleekView reads wc_orders together with the Fortnox meta keys so sync status, document number, customer number, and last sync error become sortable, filterable columns. Finance pulls every successfully synced order from last month for VAT reconciliation, ops creates a saved view for sync failed rows, and support searches by customer email to see what's pushed and what hasn't.

Inline edits to order status route through WooCommerce's CRUD layer so the integration's hooks fire and a retry sync runs as configured. Direct writes to Fortnox meta are guarded with conflict detection so manual corrections don't overwrite a fresh API callback.

Workflow

How SleekView reads your Fortnox-WooCommerce setup

1

Pick the source

Choose wc_orders for HPOS or shop_order posts on legacy. SleekView detects which path is active and exposes the matching column set plus joinable Fortnox meta.
2

Compose Fortnox columns

Add invoice number, customer number, sync status, and last error from the column picker. Only meta keys present in your data are listed.
3

Save operational views

Name them ("Sync failed last 7d", "Q2 SE invoices", "B2B by customer number") and gate by capability so finance, support, and admins each see their own table.
4

Edit inline or in bulk

Flip status through CRUD so retries fire, bulk-mark internal flags, export filtered lists for the bookkeeper. All edits run the integration's hooks as configured.

Sample columns

A typical Fortnox sync view

Joins wc_orders with Fortnox meta like _fortnox_invoice_number, _fortnox_customer_number, and _fortnox_sync_status.
Source: wp_wc_orders + wp_wc_orders_meta (Fortnox keys)
Order # Fortnox invoice Sync Customer # Total Date
#10428 FN-2026-0418 Synced FN-CUST-1042 kr 1840.00 Apr 24
#10427 (pending) Queued FN-CUST-1031 kr 725.00 Apr 24
#10426 FN-2026-0416 Synced FN-CUST-1006 kr 3120.00 Apr 23
#10425 (error) Failed FN-CUST-0987 kr 480.00 Apr 23

Comparison

Default WooCommerce Fortnox admin vs SleekView

Default WooCommerce Fortnox admin

  • Fortnox invoice number lives in wc_orders_meta and isn't visible in the Orders list
  • Failed syncs aren't a status, just an order-note buried in the order detail page
  • Last sync error message requires opening the order to read
  • No saved view for orders queued but not yet pushed
  • Fortnox customer number isn't shown next to the customer email at the row level

SleekView

  • Surface _fortnox_invoice_number and _fortnox_sync_status as columns
  • Saved view: sync failed in last 7 days for daily triage
  • Filter by Fortnox customer number for B2B reconciliation
  • Inline-edit order status to trigger a Fortnox retry through the integration's hooks
  • Export VAT-reconcilable list for the Swedish bookkeeper without leaving WP

Features

What SleekView gives you for WooCommerce Fortnox Integration

Sync status as a real column

Pull _fortnox_sync_status and the last sync timestamp from wc_orders_meta straight into the table. Failed syncs sort to the top of a saved view instead of hiding behind a normal order status.

VAT-friendly filters

Combine country, date range, and Fortnox customer number for Swedish VAT reconciliation. Save the filter as Q2 SE B2B invoices and rerun it next quarter without rebuilding.

Retry syncs through hooks

Status flips and meta edits route through WooCommerce CRUD so the Fortnox integration's listener fires and a retry runs as configured. No bypass mode, no silent direct writes.

Audience

Who uses SleekView for Fortnox Integration

Finance and bookkeeping

Quarterly view of synced orders with Fortnox invoice number and customer number, filtered by date and currency. Export to CSV for the Swedish bookkeeper without leaving WordPress.

Customer support

Search by customer email, see all orders with their Fortnox document numbers inline, and re-queue syncs if a customer reports a missing invoice.

Store admins

Daily sync failed triage view: sort by last error message, fix configuration or data, requeue. The cleanup workflow that doesn't exist in the default admin.

The bigger picture

Why Fortnox sync needs a row-level view

Fortnox is Sweden's standard small-business accounting and invoicing platform. The WooCommerce-to-Fortnox integrations are how a Swedish online store keeps its bookkeeping straight without double entry, and they work well for the happy path: order placed, invoice created in Fortnox, document number written back to WordPress. The trouble starts on the unhappy path.

A sync fails because a VAT ID is malformed, a customer record collides, or the Fortnox API hits a rate limit. The default WooCommerce Orders screen still shows the order as Completed because that's the WooCommerce status, with no surface at the row level for sync status. The error sits in an order note that nobody reads.

Three weeks later the bookkeeper notices invoices are missing for the quarter. SleekView turns the sync state into a first-class column, exposes the last error as a sortable field, and lets ops save a sync failed view as part of their daily routine. Same database, same integration hooks, dramatically less hunting for invoices that didn't actually sync.

Questions

Common questions about SleekView for WooCommerce Fortnox Integration

Any WooCommerce-to-Fortnox integration that stores its sync state and document references in wc_orders_meta or postmeta. Most of the popular ones do, including the official Fortnox-branded integration and several community variants. The column picker reads the actual meta keys present in your install, so it works with whatever your integration writes.

 

Yes. SleekView reads wc_orders and wc_orders_meta on HPOS (default since WooCommerce 8.2) and falls back to shop_order posts plus postmeta on legacy stores. The same SleekView config works across both schemas.

 

Status edits route through WooCommerce CRUD, so the integration's hook listener (typically on woocommerce_order_status_changed) fires and a re-sync runs as configured. For integrations exposing a custom sync action via a button, SleekView can attach that action as a row-level button as well.

 

No. SleekView writes to WordPress, not to Fortnox. Changes flow Fortnox-ward through your integration's existing hooks and API client. Direct writes to _fortnox_invoice_number are possible (for back-office corrections) but gated behind a per-view setting and conflict detection.

 

If the integration stores Fortnox customer numbers on WordPress users via usermeta, SleekView can present a users-rooted view with Fortnox customer number, total spent, and recent order count as columns. This is the closest you get to a CRM view without a separate sync.

 

Yes, if the integration stores VAT IDs and country codes in meta. SleekView's column picker lists keys present in your data, so VAT-relevant fields show up automatically. Combine them with date range and currency to build a quarterly VAT reconciliation view.

 

Queries hit indexed columns on wc_orders directly. Meta filters use wc_orders_meta joins, which are indexed by order_id and meta_key. Aggregate columns (total synced this month) are opt-in per view so triage views stay responsive.

 

SleekView itself is an in-admin tool, not a notification system. For alerting, hook into the integration's existing error events or use a separate notification plugin. SleekView's role is making the failed-syncs list trivially visible during normal admin work, so checking it becomes part of the daily routine.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView