Skip to content
How We Work
WooCommerce Engineering Standards
The rules our team follows on every build, from the first audit to years of maintenance, and who owns each one. They are the same standards behind the official extensions we maintain for Automattic and the carrier plugins we ship for DHL and PostNL.
19 official extensions
Maintained for Automattic since 2021, inside its review workflow
One team, launch and beyond
The engineers who build it are the ones who maintain it
The Standards
Every agency says it writes quality code. These are the specific rules we follow, who owns each one and where you can see it working.
Before we build
Audit Before We Change Anything
Every engagement starts by reading the code that’s already there: the theme, the plugins, the integrations and how they touch orders. On a takeover, that review comes before a single fix.
Proof: the Yoco rescue began with an in-depth review of the previous agency’s plugin.
Owned by Shadi Manna, Founder
Architecture Agreed Before Code
We decide where data lives, which WooCommerce APIs and hooks carry it, and how the work stays compatible with HPOS and WooCommerce Subscriptions. It goes into the written scope you approve.
Proof: the Faire integration was split into three modules (product sync, order sync and reconciliation), each solving one problem.
Owned by Dustin Parker, Lead Developer
While we build
HPOS-Safe Data Access
Orders are read and written through WooCommerce’s CRUD APIs, not direct queries against post tables, so code keeps working when a store moves to High-Performance Order Storage.
Proof: Mighty Kids moved to HPOS with zero downtime, with every plugin verified HPOS- and Subscriptions-compatible first.
Owned by Dustin Parker, Lead Developer
Payments Handled as Money, Not Data
Payment state changes go through WooCommerce’s own payment methods, with fallbacks for when a gateway’s webhook can’t be reached. An order is never marked paid by guesswork.
Proof: we replaced Yoco‘s auto-set-to-Processing logic with payment_complete() and added a webhook fallback.
Owned by Bartosz, Full-stack Developer
Measured Before and After
Performance work starts with a benchmark and ends with the same benchmark, so an improvement is a number rather than an impression.
Proof: Mighty Kids order processing went from 6s to 2.1s per order, refunds from 25 minutes to 6.
Owned by Dustin Parker, Lead Developer
Logs and Errors Your Team Can Act On
What we build logs what it does and tells administrators plainly when something is wrong, such as a failed connection or an unreachable webhook, instead of failing silently.
Proof: after logging and admin notices shipped, Yoco‘s weekly tickets fell from 30–50 to fewer than 5.
Owned by Bartosz, Full-stack Developer
After we ship
Releases That Don’t Break Stores
Code that runs on thousands of stores has to survive every WooCommerce release. Releases stay backward compatible, and migrations are timed around merchants rather than our deadlines.
Proof: the PostNL launch moved from November to February to give merchants time, and existing merchants then moved across without any major technical issues.
Owned by Abdalsalaam Halawa, WooCommerce Developer
Support Where Merchants Already Are
Support happens in public as well as in private channels. For the official DHL plugin, that means answering merchants on the WordPress.org support forum.
Proof: the DHL plugin’s support forum is public, so you can read every thread.
Owned by Saleem Summour, WordPress & WooCommerce Developer
The People Behind the Standards
Named specialists with public profiles, most of them working on official WooCommerce extensions every week.
Shadi Manna
Founder
Scopes complex projects, leads discovery and is the technical counterpart for clients including Automattic, PostNL, DHL, Faire and Yoco.
Dustin Parker
Lead Developer
Leads the development team with an architecture-first approach, including the team maintaining Automattic’s 19 official extensions. Led the Mighty Kids engagement.
Bartosz
Full-stack Developer
Eight years in distributed teams. Specializes in payment gateway architecture and works on Automattic’s live-rate and tax extensions and on Yoco’s payment gateway.
Abdalsalaam Halawa
WooCommerce Developer
Develops and maintains Automattic’s shipping and tax plugins and oversees releases for the PostNL and DHL extensions.
Saleem Summour
WordPress & WooCommerce Developer
Develops the official DHL for WooCommerce plugin and handles its public support on WordPress.org, the front line for thousands of merchants.
Luthfi Bintoro
WooCommerce Developer
Part of the team maintaining Automattic’s official extensions, specializing in customizing WooCommerce core functionality. A former Envato Elite Author.
Standards You Can Check in Public
Most agency work disappears behind NDAs. Much of ours is public: plugins on WordPress.org with open support forums and release histories.
0
major technical issues moving existing merchants to the rebuilt PostNL plugin
70%
of Yoco plugin installs on the latest version after our takeover
10,000+
products and orders synced through the Faire integration
Inspect the work: DHL for WooCommerce → PostNL for WooCommerce → Faire for WooCommerce → Yoco Payment Gateway →
“The main developer assigned to our project, Dustin, was an excellent problem solver, and implemented some very challenging feature requests.”
Mighty Kids co-founder, verified review on Clutch
Frequently Asked Questions
What engineering standards does Progressus follow?
Eight rules across the life of a project: audit before changing anything, agree the architecture before code, access orders only through HPOS-safe WooCommerce APIs, handle payment state through WooCommerce’s own methods, measure performance before and after, log clearly, release without breaking stores, and support merchants where they already ask for help.
Is your code compatible with WooCommerce HPOS?
Yes. Our code reads and writes orders through WooCommerce’s CRUD APIs, so it works with both legacy order storage and HPOS. We also migrate existing stores as a service: see HPOS migration.
Can you take over a plugin or store another agency built?
Yes, and we start with a code review rather than a rewrite. That is how the Yoco takeover began, after another agency’s payments plugin failed, and the plugin was stable within three to four months.
What happens to my code when WooCommerce releases an update?
Code we maintain gets compatibility updates as WooCommerce releases ship, from the same team that built it. That is the routine behind the official extensions we have maintained for Automattic since 2021.
How do you approach payment and checkout security?
Card handling stays with the payment provider, and payment state changes only through WooCommerce’s own methods, with fallbacks for unreachable webhooks. Payment work is led by a developer who specializes in gateway architecture.
Who will actually work on my project?
The people on this page. Shadi scopes the project, Dustin leads the build, and specialists in payments, shipping and WooCommerce core join where the work needs them.
Want These Standards Applied to Your Store?
Tell us what your store needs to do, or what's going wrong with the code it already runs. You'll get a plain answer about what's involved and what it should cost.
What happens next
- Tell us about the store and the problem. A call or an email is enough to start.
- We review the existing code and architecture before proposing anything.
- You get a written scope and a fixed quote (projects start at €2,500), or a straight answer if an existing plugin does the job.