Integrations

A plugin is a program that adds to WordPress a feature it does not have — and neither does any ready-made extension. We write that plugin from scratch, exactly for your site.

If it can be done in WordPress, it can be done as a plugin: connect the site to the system you work in, give the shop rules WooCommerce lacks, build a panel for the team, automate what somebody does by hand today. The kinds beside this are the most common orders, not the boundary.

Examples

• warehouse and order systems
• shipping carriers
• payment providers
• company registers, e-invoicing
• CRM, ERP, Google Sheets

Example integrations

BaseLinker — Orders and stock in one place.

The plugin sends shop orders to BaseLinker and takes status changes back. Stock moves both ways, so you do not sell what is no longer on the shelf. Status and warehouse mapping is set up around how you actually work.

Allegro — The shop and the Allegro listings stop being two jobs.

Shop products are tied to Allegro listings, with prices and availability kept honest on both sides. Orders from Allegro land in the shop panel like any other. Which listings sync, and how often, is your decision.

InPost — The pickup point chosen in the basket, the label from the panel.

The customer picks a locker without leaving the basket, and you print a label in one click from the order list. The tracking number goes back onto the order and out to the customer by e-mail.

PayU — A payment that does not send the customer somewhere strange.

PayU goes into the basket alongside BLIK and cards, and the payment status updates the order by itself. Anything unusual — deposits, part payments, prepayment for a service — is described in the quote before a line is written.

Przelewy24 — The same payment, a different provider.

Przelewy24 is wired in exactly as PayU is: methods in the basket, confirmation back onto the order, refunds from the panel. You can run both providers at once and decide which one handles which method.

Stripe — Cards, subscriptions and selling abroad.

Stripe earns its place where you sell repeatedly or outside Poland: cards, subscriptions, recurring charges. The plugin makes sure a notification from Stripe changes the order exactly once, even when it arrives twice.

GUS / REGON — Company details from a tax number, without retyping.

The customer gives a Polish tax number in the basket or in a form, and the plugin fetches the name and address from the register and fills the fields in. A shorter form and fewer typos on the invoice.

KSeF — The invoice goes where it has to go anyway.

The plugin prepares the invoice in the format KSeF requires, sends it, and records the reference number on the order. When it is sent, and which documents go, is fitted to your paperwork rather than the other way round.

Fakturownia — The invoice writes itself once the payment lands.

As soon as a payment is recorded the plugin creates the document in Fakturownia and mails it to the customer, keeping the link on the order. Your numbering, series and rates stay exactly as they are today.

wFirma — The same, if your books live in wFirma.

Orders arrive in wFirma as sales documents with your own descriptions and rates. Corrections and refunds too, so nobody in accounts has to straighten things out afterwards.

Google Sheets — A spreadsheet that fills itself in.

Orders, form submissions or any other event you name land in a sheet as they happen. Useful when the team works in spreadsheets and would rather not log into the shop at all.

HubSpot — A contact from the site, straight into the CRM.

A form submission creates the contact and the task in HubSpot, carrying which page and campaign it came from. Sales sees the customer's order history without switching to the shop.

Slack — The notification where you are already looking.

A new order, a failed payment or a complaint arrives in the channel you name — with what the decision needs and a link to the rest. The rules for what is sent, and when, are yours to set.

Notion — The database the team already works in.

The plugin appends records to a Notion database: enquiries, orders, content to prepare. Changes made in Notion can come back to the site as well, if that is what you need.

Mailchimp — A sign-up that matches what the customer agreed to.

The address goes onto the right list together with the consent and its date, and tags say what the customer bought and where they came from. Without consent nothing goes out, and that is a rule in the code rather than a checkbox.

Request a quote

Describe what the plugin should do. We do not need a specification — one plain sentence about what does not work today, or takes too long, is enough.

Request a quote

A fixed price for an agreed scope. We usually reply within one working day.

Other kinds

• WooCommerce — The shop does exactly what your way of selling requires.
• Gutenberg blocks — Custom blocks your editors insert like any other.
• Admin panel — Screens, tables and permissions for the people who run the site.
• Forms and submissions — Submissions land where they should, in the shape you need.
• Automations — Things somebody does by hand today happen on their own.
• Import, export, migrations — Data comes in and goes out without retyping.
• REST API and webhooks — Your site talks to apps: mobile, third-party, your own.
• Custom content types — The site knows your industry's terms, not only posts and pages.
• Memberships and access — Who sees what, and who pays for it — by your rules.
• Multilingual and localisation — One site, many markets: languages, currencies, regions.
• Repair and rebuild — We take over a plugin that stopped working or slows the site down.