FGSync for Oblio

Description

FGSync for Oblio is an independent open-source integration between WooCommerce and the Oblio.eu invoicing service. It is not developed, endorsed, maintained, or supported by Oblio.eu; Oblio is a third-party service, and an active Oblio account is required.

Documents

• Issue invoices, proformas, delivery notes and credit notes (storno), automatically or manually from the order screen.
• Proforma to invoice rule: a proforma is transformed into an invoice or deleted; a proforma is never issued after an invoice.
• Automatic credit note on WooCommerce refunds (partial and full). Experimental bridge to the WooCommerce Returns feature, activated automatically only when that feature is available in your WooCommerce version.

Performance

• Queued processing (Action Scheduler) so issuing never blocks checkout or status changes.
• Automatic retries with backoff, plus a reconciliation job for missed invoices.
• Stock synced in batches, across one or more warehouses (locations), matching the WooCommerce SKU with the Oblio product code.

Collection and notifications

• Automatic “mark as paid”, configurable per payment method, with exceptions.
• Invoices issued the moment the order reaches a status, or on a schedule (batch), your choice.
• Customer notifications two ways: a standalone email from the plugin, or a button linking to the invoice inside WooCommerce’s own order emails.

Compatibility

• Works with both High-Performance Order Storage (HPOS) and the classic order storage.
• Compatible with WPML / WooCommerce Multilingual (invoice language and currency from the order).
• Logs through WooCommerce (WooCommerce, Status, Logs) and a dedicated status panel.
• One-click import from the old “WooCommerce Oblio” plugin.

This plugin uses the Oblio.eu API. You need an Oblio account and an API secret.

External services

This plugin connects to the Oblio.eu invoicing service (https://www.oblio.eu) through its API (https://www.oblio.eu/api) to create and manage your accounting documents. Sending data to Oblio is the core purpose of the plugin and happens only for the actions you enable.

When data is sent:

• When a document is issued (invoice, proforma, delivery note, or credit note), automatically on the order status you choose or manually from the order screen.
• When an order is marked as paid (“collection”), if you enable it.
• When stock is synchronised from Oblio, on the schedule you set or on demand.
• When you test the connection or import settings from the connection screen.

What is sent for a document: your company identifier (CIF), the customer’s billing details (name, company, address, tax/registration identifiers, email and phone when present), the order lines (product name, code/SKU, quantity, price, VAT), shipping and fees, totals, and the payment method. Authentication uses your Oblio account email and API secret. No data is sent to any party other than Oblio.

Oblio service: https://www.oblio.eu
Oblio Terms and Conditions: https://www.oblio.eu/terms
Oblio confidentiality/privacy policy: it is part of the Terms and Conditions above (the “notă de confidențialitate”); the current version is published on https://www.oblio.eu

Please review those documents before use. Sending customer and order data to Oblio is subject to your agreement with Oblio and your own privacy obligations.

Upgrading from a pre-1.1.0 beta

If you installed an earlier oblio-fgwoo beta build directly (not through this wp.org listing), note before updating:

• This release ships under a new plugin slug/folder (fgsync-oblio) and main file (fgsync-oblio.php). WordPress treats it as a different plugin, not an in-place update of the old folder.
• Deactivate and delete the old oblio-fgwoo (or similarly named) plugin folder first, then install this one. Your settings, order metadata, product fields, and issued-document history are preserved: they are all stored under the oblio_fgwoo_ option/meta prefix, which this release deliberately did not rename.
• Any Action Scheduler job (document issue, refund/storno, stock sync, reconciliation) still queued or in-flight at the exact moment of the swap may need to be re-triggered manually (e.g. via “Sync now” or by re-saving the order), since the old plugin’s runtime is gone when its folder is removed. Nothing already completed (issued invoices, stored settings) is lost.
• Any custom code hooking the plugin’s filters/actions (e.g. oblio_fgwoo_email_button_issue) keeps working unchanged, since those hook names were intentionally not renamed.

Technical details