FGSync for Oblio

No. FGSync for Oblio is an independent, community-built open-source integration. It is not developed, endorsed, maintained, or supported by Oblio.eu. Oblio is a third-party invoicing service accessed through its public API; an active Oblio account is required to use this plugin.

Support is community/best-effort, through the WordPress.org support forum or the plugin’s public issue tracker (https://github.com/rwkyyy/fgsync-oblio/issues). There is no guaranteed response time or SLA.

Yes, with both HPOS and the classic order storage.

Through WordPress.org, like any plugin. There is no custom updater.

The “Conectare” tab has an “Importă setările” button that copies the old plugin’s settings. Documents already issued are shown automatically.

Three modes, under Documente. “Prin coadă” (the default) queues the invoice the moment the order enters one of the selected statuses; it’s issued within seconds, without ever slowing down that request. “Instant” issues it synchronously, in the same request that changed the order’s status (checkout, a manual status edit, a payment gateway callback), useful if you need the invoice to exist the instant the status changes, at the cost of adding a few seconds to that request; if the attempt fails for any reason, it automatically falls back to the queue, so nothing is lost. “Programat” issues invoices periodically at the interval you choose, useful when invoicing happens later, e.g. on delivery. Optionally, “Emite și la confirmarea plății” also issues the invoice as soon as an online payment (card, PayPal, etc.) is confirmed, even if the order hasn’t reached one of the selected statuses yet; it works in the queued and instant modes, like the old plugin’s automatic invoicing. In all three modes a reconciliation scan re-checks recent orders (the last 7 days by default, adjustable with a filter) and re-queues any invoice a missed hook or a brief Oblio outage skipped.

The plugin tried to issue that order’s invoice and it failed; hover the badge on the orders list (or open the order) to see the stored reason. Recoverable failures are retried automatically through the reconciliation scan and Action Scheduler’s own backoff. If the reason points to something on the Oblio side (for example, insufficient stock in the linked gestiune), fix it there, then re-issue manually from the order screen.

Oblio only allows deleting the last document issued in a series. If a newer invoice already exists in the same series, the delete button is hidden for the older one; issue a storno (credit note) instead to reverse it. Proformas are the exception: they can always be deleted, since Oblio treats them separately from the numbered invoice series.

It is taken off the invoice: refunded quantities and amounts are left out, and a refund by amount only shows as a discount line. That refund gets no separate credit note. An order refunded in full before invoicing gets no invoice. If the invoice is built on a delivery note or proforma issued before the refund, it keeps that document’s values and the refund gets a credit note as usual.

Under Avansat, “Produse pachet (Bundles)” controls this. The default, “AUTOMAT”, invoices the bundle’s individual components, not the bundle product itself, because the bundle product usually has no stock record of its own in Oblio, and deducting stock against it fails. If the bundle has its own price (a fixed-price or promotional bundle, with the components at 0), that price is split across the components, weighted by their regular prices, so the invoice total matches the order and stock still comes off the real products. Partial refunds of such a bundle are credited on the same components, in the same proportions. If your store doesn’t deduct stock through Oblio, “INCLUDE linia pachetului” is worth trying instead: it shows the bundle as a single line with its own name and price, which often reads more clearly on the invoice.

One per VAT rate your shop uses, under Oblio → Setări → Cote TVA. The plugin matches them by percentage, not by country or name, and the TVA tab lists any rate that has no category yet, with the recommended name (the rate itself, for example “25.5”). After adding one, press “Preia ultimele date” on the Conectare tab.

Oblio does not allow editing a VAT category once an invoice uses it, so add a new category for the new rate (for example “21” next to “19”) and keep the old one. Update the rate in WooCommerce → Setări → Taxe, by hand or with the EU import button. New orders then use the new category; invoices already issued keep their original rate, and documents for orders placed before the change still use the old category. Which rate applies to an order placed before and invoiced after a change is a question for your accountant: the plugin uses the rate recorded on the order.

No. WooCommerce calculates the VAT on the order (by your tax settings and any VAT exemption plugin), and FGSync sends that rate to Oblio unchanged. Rules such as OSS, reverse charge for EU companies, or exports are configured in WooCommerce and agreed with your accountant. If taxes are turned off in WooCommerce, lines are sent without a VAT rate and Oblio applies your account’s own settings (for example, not a VAT payer); the TVA tab then shows only the OSS and customer settings.

FGSync does not check VAT numbers in VIES. Use a checkout plugin that validates the customer’s EU VAT number in VIES and removes the VAT from the order; FGSync then sends those lines at 0% with the category chosen in the TVA tab (for example “Taxare inversa”). Keeping proof of the VIES check for your records is up to that plugin and your accountant.

Under TVA, when enabled, documents for a billing address outside Romania (in the EU or elsewhere) are issued in EUR regardless of the order’s currency, with Oblio showing the RON equivalent alongside it. It changes only the currency, never the VAT: the VAT still comes from WooCommerce. It’s off by default; whether EUR invoices suit your store is a question for your accountant.

If “Rezervă stoc pentru comenzi nefacturate” is enabled (Sincronizare tab), the stock WooCommerce displays is reduced for pending/processing orders that haven’t been invoiced with stock deduction yet, so the store doesn’t oversell while waiting. The actual deduction inside Oblio only happens once an invoice is issued with stock deduction on; this setting only affects what WooCommerce shows as available in the meantime.

A shortcut to the FGSync “Stare” tab, with a small colored dot: green means everything’s normal, yellow means the processing queue has a large backlog, and red means the last attempt to reach Oblio failed (it clears as soon as a later call succeeds). It’s on by default; turn it off from a checkbox on that tab.

Under Email, pick a mode. “Email separat (la emitere)” sends a separate message from the plugin when the document is issued, using your subject/message templates. “Nativ în mail-ul WooCommerce” instead adds a button linking to the Oblio invoice inside WooCommerce’s own order emails, for the order statuses you select (for example, the Completed order email). In that mode, if the invoice has not been issued yet when that email is sent, the plugin tries to issue it at that moment, even when automatic invoicing is off, so the button usually links to a real invoice. If Oblio’s rate limit is busy or that attempt fails, the invoice is queued instead and that particular email goes out without the button; the invoice itself still gets issued shortly after. Use the oblio_fgwoo_email_button_issue filter to disable the inline attempt if you only want a button when an invoice already exists.

Yes. A few examples: oblio_fgwoo_stock_quantity and oblio_fgwoo_stock_price adjust a value right before it’s written during stock sync, oblio_fgwoo_document_currency and oblio_fgwoo_document_language override those per order, and oblio_fgwoo_email_button_issue (see above) controls the email button’s inline-issue behavior. See the plugin’s GitHub repository (https://github.com/rwkyyy/fgsync-oblio) for the current list.