- Can I use softsolutions4u/orocommerce-invoice in a Laravel application?
- No. This is an OroCommerce bundle built on Symfony, not a Laravel package, and there is no Laravel compatibility path. It installs into an OroCommerce CE 7.0 application via Composer plus oro:platform:update and oro:assets:install. If your stack is Laravel, the evaluation ends here regardless of feature merit.
- How do I install the OroCommerce invoice bundle?
- Composer require softsolutions4u/orocommerce-invoice, then run oro:platform:update and oro:assets:install. The documented install path uses oro:platform:update --force, which bypasses platform integrity checks. Get a written explanation of why --force is required before putting that step in a production runbook.
- Which OroCommerce, PHP and Symfony versions does it support?
- It targets OroCommerce CE 7.0.3 but declares PHP 8.5 and Symfony 7.4, the newest majors in their lines. That combination suggests either a very recent build or an untested lower bound. Ask the vendor for a real compatibility matrix covering the 7.0.x patch range, PHP 8.3 and 8.4, and Symfony 7.2 and 7.3, plus any 7.1 roadmap.
- What invoice statuses and state machine does the bundle implement?
- The workflow moves Draft to Posted to Open, then Partially Paid or Overdue, and finally Paid, with a Cancelled branch. Actions are ACL-gated and the bundle ships its own email templates. It is not documented whether the Overdue transition runs on cron, a message queue, or lazy evaluation, or whether that is configurable and observable.
- Does it support online payments and partial payments?
- Yes, it supports full or partial online payment from the storefront, plus offline Payment Term and Money Order settled by an admin. The payment service provider is not named, so PCI DSS scope is unknown and the difference between SAQ A and SAQ D matters a lot here. Partial payments combined with a storefront retry button is a classic duplicate-charge surface, and idempotency keys or double-submit protection are not documented.
- Does it guarantee gapless sequential invoice numbering for EU VAT or German GoBD?
- The release notes say nothing about numbering strategy, gap handling under concurrency, or multi-year retention. Invoicing is a regulated artifact, so sequential, unique, monotonic numbering is a legal requirement in many jurisdictions. Ask whether numbering is configurable per organization or website and how uniqueness holds under concurrent order placement.
- Can I edit an invoice after it has been posted?
- Immutability after Posting is not documented, and neither is the correction path. Ask the vendor explicitly whether a Posted invoice can be modified, and whether corrections are handled by credit memo, cancellation only, or direct edit. The answer determines whether the bundle can satisfy audit requirements in your jurisdiction.
- Does it generate PDF invoices and send email notifications?
- Yes. It produces PDF invoices and ships four email notification types with its own templates, plus EN and DE translations. The bundle is self-contained and claims no core overrides, which is the key claim for staying upgradeable alongside the platform. That claim is unverified at v1.0.0, so validate it before committing.
- Is softsolutions4u/orocommerce-invoice production ready and actively maintained?
- It is a v1.0.0 single-vendor package with a very wide first-release surface: backoffice, storefront, payments, PDFs, four email types, auto-invoicing and RBAC. The supplied data shows no test coverage, CI, static analysis, security disclosure policy, or license terms. A bundle that moves money and issues tax documents needs more evidence than a README, so ask for the test suite and support SLA.
- Does it support multi-organization, multi-currency and multi-website setups, or an ERP export?
- These behaviors are not documented in the supplied material. Ask whether invoices can be scoped per organization, website and currency, and whether OroCommerce is intended as the system of record. If you need accounting reconciliation, confirm whether an export or API surface exists for ERP integration.