This is a build-to-order product, not an instant download. After we confirm your requirements (document types, branding, numbering, tax setup and which order statuses trigger emails), a typical build is delivered in about one working week. We develop against a copy of your store, test on a staging site, then ECOSIRE installs and activates the plugin on your live WordPress site and verifies it against real orders. You receive the packaged plugin ZIP and the source code for your site.

Yes. Every build includes a post-launch support window covering bug fixes and compatibility checks against new WooCommerce and WordPress core releases. Because the plugin reads and writes order data through WooCommerce's CRUD/HPOS APIs rather than the database directly, it is resilient to core updates. After the included window you can opt into an ongoing maintenance arrangement, or request changes (new document types, layout updates, extra integrations) as scoped follow-on work.

Yes. The plugin is declared HPOS-compatible and accesses orders only through wc_get_orders() and the $order object, so it works whether you use legacy post-based orders or the new custom order tables. We test it alongside your existing stack — payment gateways, shipping, subscriptions and any plugins that add custom order statuses — and hook into those statuses so invoices and packing slips fire at the right moment.

That is the main reason to build rather than buy off-the-shelf. We configure logo, colors, company details, footer terms and custom CSS in the template builder, and we set up your tax display — multiple tax classes, VAT/GST/Tax-ID labels, reverse-charge or zero-rated notes — to match your jurisdiction. If you need a layout an off-the-shelf plugin can't produce, we build it, because we own the template code.

Yes. The build includes a WooCommerce REST API endpoint that returns a given order's invoice or packing slip PDF, so your ERP, 3PL, or accounting tool can fetch documents programmatically. Documents are also archived as a custom post type and can be stored in a protected uploads directory or an S3-compatible bucket with signed URLs, so they are never publicly guessable. We scope the exact integration with you during the build.