Choose Magento Modules by the Store Task You Need to Complete
Start with the job your Magento store needs to do. A catalogue editor fixing category descriptions, a buyer choosing a compatible accessory and a bookkeeper reconciling invoices need different workflows. Your existing Magento tools may already cover the task; add a module when its supported operation closes a specific gap.
This map is for merchants and agencies improving an existing store, especially technical and industrial catalogues. The eight routes below are task groupings, not commercial bundles or instructions to install everything. Their sequences are illustrative and unexecuted; no combined deployment, customer result or integration test is claimed.
Maintain the catalogue: identify the record first
Illustrative scenario: an equipment distributor renames a category, introduces a connector attribute and moves selected products into a new range. These are category records, attribute definitions and product assignments, respectively.
Use the native category editor for a few records or an existing parent move, native attribute screens for a small schema, and product CSV or Update Attributes for supported product-value changes. For larger reviewed batches, begin with category-record CSV and attribute definitions; then review product values and complete category assignments. Use grid actions for a deliberate selection.
Category Manager cannot re-parent existing categories by CSV. Blank replacement-category cells leave links unchanged. BPO's grid price action sets a fixed value and has no general undo. Bring a small export, intended store scope and an expected-results list; inspect saved records, translations, navigation and URLs after each stage.
Hand over CMS content: pages and blocks stay separate
Illustrative scenario: an agency hands over a full inspection-services page and a reusable servicing notice for two store views. Native CMS editing may be enough for those two records; a developer-managed patch may suit release-owned content.
For recurring spreadsheet handovers, use the CMS block and page guide. Export each entity through its own module, retain the originals, review identifiers and store codes, import a small sample and compare the rendered destinations. Pages carry supported metadata and layout; blocks are reusable content consumed elsewhere.
Move media separately: CSV contains HTML references, not image files. Matching identifiers and All Store Views assignments need deliberate review. Common script-pattern filtering is not complete sanitisation. Bring one representative page, one block, target store codes and required media paths; use trusted editors and inspect the saved HTML and public result.
Help buyers select products: data before a finder
Illustrative scenario: a maintenance buyer knows an instrument's series and model but needs the correct accessory. Native layered navigation may answer the question without another interface.
If question order helps, verify the source compatibility table, complete the relevant attributes and configure a guided finder. Compare known no-match, single-match and multiple-match paths. Add public manuals or drawings where buyers need evidence. Use option templates only for suitable add-ons such as a service choice.
The finder filters data; it does not certify physical fit. Group-filtered document links do not make files private, and custom options do not create separately stocked variations. Bring manufacturer-backed mappings, representative SKUs and a public document. Review optional combination URLs for usefulness rather than generating indexable pages for every possible selection.
Handle enquiries, quotes and shipping as distinct decisions
Illustrative scenario: a buyer asks whether a cable assembly suits an installation, then requests a negotiated quantity. A native contact form and manual response can cover a simple question. Native table rates may already cover straightforward shipping.
Use a structured enquiry form when specific answers are needed. Use catalogue RFQ when staff must negotiate product lines. After agreement, verify the checkout handoff, then evaluate shipping bands and methods against actual destinations, weights and totals.
A form is not an automatic quote connector, a quote is not an order, and a shipping-row preview is not a cart quote. Uploaded form files use public media URLs. Bring one enquiry, a sample trade basket and boundary postcodes; check tax, shipping, payment, group visibility and failed paths. Price hiding is not universal protection across feeds and APIs.
Manage orders and accounting: choose one reconciled route
Illustrative scenario: a distributor needs staff notes and recognisable references, while its bookkeeper wants reviewed sales invoices. Native order screens and a manual or reviewed CSV handoff may meet the volume.
Use order operations for the supported staff workflow and document numbering only where integrations can accept the format. If direct transfer is needed, review Xero connection, mapping and invoice triggers with the bookkeeper before sending data.
Do not blindly process the same orders through CSV and API routes. Confirmed invoice IDs help recognise repeats; uncertain responses still need inspection. Changing status or deleting an order does not undo payment or fulfilment. Bring redacted order/invoice examples, tax mappings and downstream reference rules. Refunds, payments, credit terms and reconciliation need explicit scope.
Trace communications before changing transport
Illustrative scenario: a buyer reports a missing order email, while a service enquiry has no visible reply. Native email settings, cron checks and the existing mailbox may be sufficient to locate the fault.
Follow the email diagnostic route: establish whether the message was created, queued, relayed and received. Use cron history when scheduling is implicated and SMTP for an appropriate transport connection. Choose tickets for managed conversations, separately from form intake.
A successful send is not guaranteed inbox delivery. Rerunning jobs can repeat effects, and replies to ticket notification emails are not ingested into the thread. Bring timestamps, a controlled test address, redacted message headers and the expected response owner. Keep queue, relay and received-message evidence separate.
Make useful advice easy to find and check
Illustrative scenario: a technical supplier explains how to choose an inspection camera. A useful native CMS page with clear navigation and relevant links may be enough.
For ongoing editorial work, use a maintained blog, connect answers to products and guides, and review human and XML sitemap roles. Check titles, canonical URLs, active destinations and accessibility. Optional llms.txt outputs are supplementary summaries, not crawler access control or a requirement for AI search.
Content needs accurate evidence; indexing, ranking and citations are not guaranteed. Image optimisation also needs actual delivery of generated formats. For shopping feeds, a generation issue remains unresolved: require successful generation and validation on the exact buyer-delivered build before relying on it. Bring a real buyer question, supporting sources and sample output; channel acceptance is a separate check.
Review the product story before promoting it
Illustrative scenario: a supplier launches a new test instrument using an approved fact sheet. Manual editing and the merchant's existing publishing tools may cover the whole job.
Where helpful, use simple-product drafts for initial records or field drafting for existing content. A reviewer checks units and unknowns before saving. Verify badge claims, then review the script and transcript for an optional voice guide. Campaign drafts and shopper sharing buttons serve different distribution tasks.
These are not an automatic connected pipeline. Provider usage and scheduling services can have separate charges. A draft or scheduled item is not publication evidence; sharing buttons do not run a merchant campaign. Bring the approved source revision, review owner and existing reusable media. Changed facts can invalidate copy, recordings and promotions.
All 32 Luma-compatible module and support entries
Current direct-store versions below reflect the 4 November 2026 inventory. Follow the task guide for detail, then check the exact delivered package and its product/installation guide. Magento Open Source 2.4.9 is the catalogue baseline, not certification of every PHP version, theme or combined deployment. Recorded walkthroughs and Adobe delivery can use different versions.
| Module / task guide | Direct version | Smallest useful job and limit |
|---|---|---|
| Bulk Product Operations | 1.0.3 | Selected grid changes; fixed-value prices, no general undo. |
| Category Manager | 1.0.4 | Category records; no existing parent moves by CSV. |
| Import Category Replace | 1.0.3 | Complete product memberships; blank cells leave links unchanged. |
| Attribute Import / Export | 1.0.3 | User-defined definitions; separate from product values. |
| CMS Block Import / Export | 1.0.3 | Reusable block records; basic HTML filtering. |
| CMS Page Import / Export | 1.0.4 | Page records and metadata; media moves separately. |
| Product Fit Finder | 1.0.9 | Guided attribute choices; not physical-fit certification. |
| Product Documents | 1.0.5 | Reusable public files; not confidential storage. |
| Global Custom Options | 1.0.2 | Owned option templates; not separately stocked variants. |
| LabelsPro | 1.0.10 | Targeted badges and banners; claims need verification. |
| B2B Suite | 1.0.6 | RFQ and negotiation; verify checkout and price surfaces. |
| Custom Forms | 1.0.3 | Structured enquiries; uploaded files use public URLs. |
| Shipping Matrix | 1.0.2 | Configured shipping bands; verify actual cart totals. |
| Order Manager | 1.0.3 | Staff order operations; not payment reversal. |
| Custom Order Numbers | 1.0.9 | Document references; check uniqueness and integrations. |
| Xero Connect | 1.0.3 | Invoice transfer; reconcile mapping and uncertain responses. |
| SMTP Email Delivery | 1.0.4 | Mail transport; not guaranteed inbox delivery. |
| Cron Manager | 1.0.10 | Inspect jobs; reruns can repeat effects. |
| Support Tickets | 1.0.5 | Managed threads; notification-email replies are not ingested. |
| Social Login | 1.0.5 | Supported provider sign-in; verify callbacks and linking. |
| GDPR Pro | 1.0.3 | Choice/request workflows; not automatic legal compliance. |
| Blog Pro | 1.0.5 | Buying advice; review facts and keep links current. |
| HTML Sitemap | 1.0.11 | Customer navigation; XML sitemap has another role. |
| Image Optimisation | 1.0.4 | Generate formats; delivery integration still required. |
| LLMs.txt Generator | 1.0.10 | Optional summaries; no guaranteed AI use or citation. |
| Product Feeds | 1.0.7 | Generation issue unresolved; require exact-build validation before use. |
| AI Content Optimiser | 1.0.3 | Reviewed field drafts; separate provider usage charges. |
| AI Product Creation | 1.0.4 | Simple-product drafts; review before enabling. |
| Voxfunl | 1.0.0 | Reviewed voice guide and transcript; regenerate stale audio. |
| Omnichannel | 1.0.3 | Channel drafts; connected delivery needs separate verification. |
| Social Share | 1.0.3 | Shopper product links; not campaign publishing. |
| Core — free support | 1.0.3 | Shared dependency only where the exact package requires it. |
Do I need one module, a scoped store refresh or a migration?
Module only: retain the current storefront and address one demonstrated gap. Install only the dependencies required by the exact package. Core is free shared support where required; it is not a paid prerequisite for every standalone module.
Scoped store refresh: agree a bounded set of content, catalogue, navigation or configuration changes with your implementer. Name the pages, records, integrations and acceptance checks. This is project work, not a bundle implied by this task map.
Frontend migration: assess the separate Astro architecture and Suite buyer journey. Luma-compatible templates do not automatically become Astro interfaces. Define data sync, checkout, accounts, email returns, hosting and rollback. The implementation scope guide separates software from migration, training and custom work; current product offers govern inclusion.
What should I bring to a fit conversation?
Bring Magento/PHP versions, theme and relevant extension names; one redacted product/file/cart example; the expected outcome and a failure case; and who owns review and daily operation. Explain what native tools already do and the remaining gap. Keep credentials, customer data and confidential files out of the enquiry.
Ask about the smallest suitable route. Request a scoped demonstration against your example and distinguish what is configured, integrated, tested or still excluded. This map describes AgenticEcom's own offers; it promises no delivery date, revenue, search outcome or universal compatibility.
Product information reviewed 4 November 2026 by AgenticEcom. Illustrative examples are not customer results or new runtime tests.