WooCommerce · plugins and customisation
A WooCommerce plugin the catalogue lacks.
The site runs on WordPress, the store on WooCommerce, and the plugin you need does not exist or does half the job. We write shipping, payment and fiscal plugins, marketplace feeds and exchange with 1C and Dynamics 365.
One plugin for your process.
An off-the-shelf shipping plugin does not know your carrier, and an off-the-shelf payment plugin does not know your bank. Your own knows both and is updated along with the store.
The price is known before the code.
A functional specification, then a fixed price. A weekly demo on a copy of the store.
The code is yours.
The plugin lives in your repository; hosting and WordPress access stay with you.
What we write for WooCommerce
Shipping.
A carrier plugin: the waybill is created from the order, the tracking number stays on the order, and the customer picks a branch or parcel locker in the cart.
Payment and receipt.
A payment gateway for a local bank or QR payment. A fiscal receipt for every online payment, as in our Vchasno.Kasa for Shopify.
Marketplaces.
A feed to the marketplace's requirements, with stock updated on a schedule. An error log shows which product lacks a category or a required field.
Checkout and exchange with the books.
Your own checkout fields: delivery date and time, pickup point, courier instructions. Products, stock and prices go from 1C or Dynamics 365 to the store; orders and payments go back.
How the work goes
A conversation about the task.
45 minutes. You show an order the manager finishes by hand today; we say which of it the plugin will take over.
Functional specification.
Screens, fields, exchanges, access rights. One page for the manager and a specification for the developer. The price is fixed.
Development in plain view.
A weekly demo on a copy of the site with your products and orders.
Launch and support.
Installation on the live site, handover of code and access. Support is billed monthly.
Moving to WooCommerce
We move products, customers and orders from another platform as a project. A ready-made app exists for one route only: from Prom.ua to Shopify.
What we do not do
We do not assemble a site from a theme and other people's plugins. If a ready-made plugin from the WordPress catalogue covers the task, we will say so on the first call.
Where to start
Show us an order the manager finishes by hand today: copying it into the carrier's portal, issuing the receipt, entering it in 1C. That is where we start.
Questions about WooCommerce plugins
Does Master Development build WooCommerce plugins?
Yes. Master Development writes WooCommerce plugins to order: shipping, payment, fiscal receipts, marketplace feeds, exchange with 1C and Dynamics 365. The price is fixed after the functional specification.
Can WooCommerce be connected to 1C or Dynamics 365?
Yes. Master Development writes the exchange between WooCommerce and the accounting system: products, stock and prices go to the store, orders and payments go back.
Shopify or WooCommerce?
WooCommerce when the site already runs on WordPress and you need full control of the code. Shopify when launch speed matters and apps install from the catalogue. Master Development works with both platforms and with OpenCart.
Who owns the plugin after development?
The client. The code, the repository and WordPress access stay with the client; Master Development works inside them.
Describe the plugin in three sentences.
We will say what it will take over and how big the job is.