Why Wareferry exists.
I built it because most fulfilment connectors work the other way round, and that always bothered me.
To plug a warehouse into a WooCommerce store, the usual connector asks you to hand over an API key, or to create a Shop Manager account for someone else’s system. From then on that system can read your whole store whenever it likes: every order, every customer, every product. The keys live somewhere you do not run and cannot audit. For a convenience I only needed in one direction (send this order out), that felt like far too much to give away.
So Wareferry does the opposite. The plugin runs inside your store and pushes each order to the warehouse with the minimum data to ship it: the SKUs and the address, and nothing else. The warehouse never gets a key, never gets admin, never gets a way back in. It is the same idea the GDPR calls data minimisation (art. 5.1.c), applied to fulfilment.
One shared core, one small adapter per warehouse. That way the hard part (the orders, the tracking, the batches, the privacy) is written once and tested once, and each fulfiller is just the part that speaks its own API. A store can run several at once, with one panel and one column, and switch between them without a migration.
A developer, not a platform.
Wareferry is made by David Marín Carreño, a freelance developer who has been building for WordPress, WooCommerce and the Spanish web for twenty years, under the name DaveFX. He has integrated online stores with 3PLs and fulfilment warehouses in real projects, including Invenco, James and James and JD Logistics, so the problems Wareferry solves are ones he has met first-hand. It is not a VC-backed platform that needs your data; it is a set of plugins that do one job and get out of the way. The free version really works, with no limits and no trialware, and I am honest about what is ready and what is not.
Follow the build.
The plugins are in development. Join the waitlist and I will tell you when the first one ships.