Admin Actions / Audit Log

This is a build-to-order extension, not an instant download. Typical delivery is 5–10 business days depending on your Magento version (Open Source or Adobe Commerce), any custom entities you want tracked, and environment access. After a short scoping call we build and unit-test the module, then install it on your staging environment for sign-off before production. You receive a firm timeline in writing before work starts.

Every build includes a warranty period for bug fixes, plus optional ongoing support. Because ECOSIRE delivers the source code, you own the module. We provide compatibility updates for Magento minor/security releases on request and can extend the captured entity scope or retention rules as your store evolves. Support is handled directly by the engineers who built it — there is no third-party marketplace queue.

Yes. The module targets the standard Magento 2 framework (DI, plugins, observers, service contracts, declarative schema) so it runs on both Magento Open Source and Adobe Commerce. On Adobe Commerce it complements — rather than conflicts with — the built-in Admin Actions Log by adding field-level diffs and rollback. We confirm your exact version and edition during scoping and test against it.

No meaningful impact for normal use. Capture happens on the existing save/delete and dispatch flow with indexed inserts; high-volume work like bulk imports can be excluded from capture via configuration so a 50,000-row product import does not bloat the log. The auto-cleanup cron keeps the table bounded, and the schema is indexed for fast filtering even with millions of rows.

Each change stores a serialized snapshot of the entity (or the specific changed fields) before and after. Rollback re-applies the prior value through the same repository service contracts, so it respects validation and indexing rather than writing raw SQL. Rollback is gated behind its own ACL resource, so you can grant view-only audit access to most admins and restrict rollback to senior staff. The rollback itself is also logged.

Yes. You can export any filtered view to CSV or XML directly from the admin grid, and there is a read-only REST endpoint to pull entries programmatically into a SIEM/SOC pipeline or scheduled report. Records include user, role, IP, URL, timestamp, store view and object reference, which is typically what auditors expect for privileged-access accountability.