Skip to content

Commerce

WooCommerce integration

Connects your WooCommerce shop to invoicing, Portuguese payment methods and carriers through webhooks and the REST API.

Overview

WooCommerce

WooCommerce is the most common online shop among small Portuguese businesses, because it runs on WordPress and there is a plugin for almost everything. The cost is a slow shop, clashing plugins and updates that break invoicing at the worst moment.

Tejobit moves that work out of WordPress. The connection listens to WooCommerce webhooks such as order.created and order.updated, and uses the REST API to read and update orders, customers and products. Invoicing, shipping and stock then run outside the shop, unaffected by plugin updates.

When an order moves to Processing, the invoice is issued. When the label is created, the tracking number goes back to the order and into the customer's email.

Use cases

What it is for

  • A natural cosmetics shop issuing the Moloni invoice once an order is paid
  • An online wine shop requesting the CTT label and emailing tracking to the customer
  • A clothing brand sharing stock between its physical store and WooCommerce
  • A shop showing Multibanco references at checkout and moving on only after the callback
  • A business that also wants orders in a sheet for the warehouse team
IN

What the connection listens to

  • order.created webhook for new orders
  • order.updated on status changes (processing, completed, refunded)
  • product.updated for price or stock changes
  • Payment confirmation from the gateway
OUT

What the connection does

  • Issue an invoice or invoice-receipt in the invoicing program, using the checkout tax number
  • Create the shipment with the carrier and save the tracking number on the order
  • Update order status through the REST API
  • Sync stock with another channel or the warehouse
  • Create credit notes on refunds

How it works

From the request to a working connection

  1. 01

    Request

    The form names the integration, the tools involved and what should happen in each case.

  2. 02

    Review and proposal

    Tejobit confirms what the API allows and sends a proposal with the flow, the price and the timeline.

  3. 03

    Setup and testing

    The connection is set up with the business's own accounts and tested with real cases before it goes live.

  4. 04

    Maintenance and monitoring

    Tejobit hosts the connection, follows up on errors and adapts it when the API changes.

The connection runs on Tejobit's infrastructure. The monthly fee covers hosting, monitoring and API changes.

What to prepare

  • WooCommerce REST API keys (consumer key and secret) with read and write access
  • A tax number field at checkout, if the shop does not have one yet
  • Status rules: when to invoice and when to ship
  • Access to the invoicing program and carrier accounts

For security, do not send passwords, API keys or tokens through the form. Credentials are requested through a secure channel when the setup starts.

Limits

  • WooCommerce webhooks rely on WordPress cron and can lag on weak hosting
  • Plugins that alter orders or checkout can change the data format and need adjustments
  • The shop needs HTTPS, and security plugins must not block the REST API

Frequently asked questions

Before you start

Why not just use an invoicing plugin?

Plugins work until they don't, usually after an update. With the connection outside WordPress the shop stays lighter and invoicing does not stop over a conflict.

Does it work with HPOS?

Yes. The connection uses the REST API and webhooks, which behave the same with high-performance order storage.

What if a webhook fails?

WooCommerce disables webhooks after repeated failures. The connection also checks the REST API on a schedule to catch any order that slipped through.

Can I invoice paid orders only?

Yes. The invoicing rule follows the order status, for example only on Processing or Completed.

Set up the WooCommerce integration?

Describe what should pass between the tools. The reply confirms feasibility, price and timeline.