ShipEasy: Orders Grid Columns, ShipRules and Setup

This page is part of the ShipEasy guide. Start there for what the extension does, installation and the frequently asked questions.

#Add custom columns to the orders grid

Display richer data on each order row so your team can act without opening individual orders.

#How to set it up

1. Go to: Stores > Configuration > Moogento > ShipEasy > Orders Page: Columns

2. The column picker interface lets you drag columns into position and toggle their visibility. Enable the columns your team needs - common choices are SKUs, Product Images, Stock, Revenue, Tracking, Tags, Customer, and Priority (Pro).

3. Save config, then run php bin/magento cache:clean.

#Notes

• The number of columns available depends on your plan: Seed includes core columns, Growth adds more, and Pro adds priority and ShipRule tag columns.
• Custom product attribute columns (shelf location, colour, size) are available on Pro. Configure the attribute code in the Columns picker.
• You can also manage columns from the CLI: php bin/magento moogento:shipeasy:columns.

#Set up ShipRules to auto-route orders to carriers

Automatically tag each order with the carrier or packing method it should use, based on weight, dimension, postcode, or shipping method.

#How to set it up

1. Go to: Stores > Configuration > Moogento > ShipEasy > ShipRules: Setup

2. Set Enable ShipRules? = Yes.

3. Set Weight unit of measure to match the unit used on your products (e.g. grams, kg, lbs). This is a display label - the number entered in each rule must match your product weight unit.

4. (Optional) Set Product attribute: Max Dimension to the attribute code on your products that holds the maximum physical dimension. Needed only if you want to match rules by size.

5. Click Save Config.

6. Go to: Stores > Configuration > Moogento > ShipEasy > ShipRules: Rules

7. Add one rule per carrier or routing scenario. Each rule can match on weight range, max dimension, shipping method, postcodes, and SKU count. Give each rule a descriptive name - the name appears as the order tag in the grid.

8. Save config and run php bin/magento cache:clean.

#Notes

• The ShipRules engine runs via cron every 5 minutes. New orders receive their tag automatically; existing orders update on the next cron cycle.
• To test a rule against a specific order before going live: php bin/magento moogento:shipeasy:shiprules --action=set-for-order --increment-id=100000123 --dry-run.
• ShipRules is a Pro plan feature. The engine setup fields are visible on all plans but rule processing requires a Pro license.

#Import tracking numbers from a carrier CSV

Requires Growth or Pro. Upload a file from your carrier or 3PL to add tracking numbers to many orders at once.

#How to set it up

1. Go to: Stores > Configuration > Moogento > ShipEasy > Process: CSV

2. Set Show 'Process: CSV' button in Orders page? = Yes.

3. Configure the CSV column name mappings to match the column headers in your carrier's export:

   • CSV column title for: Order ID - the column header that holds Magento order increment IDs (required)
   • CSV column title for: Tracking Info - the column header that holds tracking numbers
   • CSV column title for: Carrier Title - the column header that holds carrier names (optional)
   • CSV column title for: Carrier Code - the column header that holds marketplace carrier codes such as ups or AMZL_US (Pro plan, optional)
   • CSV column title for: Sku and CSV column title for: Qty - for partial shipments
   • CSV column title for: Admin Comment and CSV column title for: Customer Comment - to write comments from the CSV

4. Save config.

5. In the orders grid, click Process: CSV, upload your file, and review the import results.

#Notes

• Every row in the CSV must have an Order ID. Rows without an Order ID, or rows where the order ID does not match any Magento order, are reported as failed and skipped.
• A row is only counted as successful after the order has been loaded and updated. Rows with blank order identifiers or unrecognised order numbers appear in the failed-rows list.
• To notify customers when a second or third tracking number is added: set Send specific transactional email if 2nd/3rd/etc. tracking number added? = Yes.
• The Delivered By Date (DBD) column requires TrackEasy Growth or Pro installed; date format must be Y-m-d (e.g. 2024-05-27).
• When carrier auto-detection is enabled (see below), ShipEasy infers the carrier from the tracking number format when the carrier name column is absent or unrecognised.

#Enable carrier auto-detection for CSV imports

ShipEasy can automatically identify the correct carrier - Royal Mail, UPS, Evri, Amazon Logistics, USPS, and more - from the tracking number's format instead of requiring a carrier name column in every CSV row.

#How to set it up

1. Go to: Stores > Configuration > Moogento > ShipEasy > Process: CSV

2. Confirm Show 'Process: CSV' button in Orders page? = Yes.

3. Check Carrier auto-detection: Enable pattern detection? is set to Yes (it is on by default).

4. Review the Carrier auto-detection: Pattern rules table. The built-in rules cover the most common UK carriers (Royal Mail, Evri, Yodel, Amazon UK, UPS). US and Australian patterns (AMZL US, USPS, AusPost) and broad numeric patterns (FedEx, DHL, DPD) are present but disabled by default to avoid false positives - enable them if your store ships with those carriers.

5. To add a pattern for a carrier not in the list:

   • Click Add row in the pattern table.
   • Enter a PCRE regex fragment (no delimiters) that matches your carrier's tracking number format.
   • Enter the carrier code (e.g. mycarrier) and a display name.
   • Set a priority lower than any existing rule you want this to beat (lower number = higher priority).
   • Save config.

6. To test a tracking number against the active patterns, use the Test button in the pattern table row.

7. Set Carrier auto-detection: Fallback carrier code and Fallback carrier title to the carrier name used when no pattern matches. Use a real carrier name such as Local Courier - do not use Custom as Amazon treats that as an invalid carrier.

8. (Optional) Enable Carrier auto-detection: Log detection decisions? alongside the General log to write per-row detection results to var/log/moogento_shipeasy.log.

#Notes

• Built-in patterns updated by a future module upgrade will only refresh rows that you have not edited (rows where created and updated timestamps match). Your custom edits are preserved.
• UK Amazon Shipping text in the carrier column resolves to amzl_uk. If your store is US-based, supply AMZL_US or amzl us in the carrier column, or use the CSV column title for: Carrier Code field (Pro plan) to pass the marketplace carrier code directly.
• For large CSV imports processed in multiple AJAX chunks, the final summary line showing "N rows saved as custom carrier" reflects only the last chunk. The per-row warning messages in the progress log are the reliable signal for multi-chunk imports.

#Enable row colorising by order status

Give your team an instant visual read of the orders grid without scanning individual status labels.

#How to set it up

1. Go to: Stores > Configuration > Moogento > ShipEasy > General

2. Set Colorize order rows based on status? = Yes.

3. (Optional) Set Hover Highlight Percent under Orders Page: Row Colors to adjust how much lighter or darker a row becomes on hover.

4. Save config and run php bin/magento cache:clean.

#Notes

• Colors are driven by the order status assigned to each row color slot. Edit the color hex values in the Row Colors group.
• The tighter grid layout options (Use ShipEasy grid design, in all admin grids? and Use ShipEasy grid design, in the Orders page?) can be enabled in the same General group. The all-grids option is a Pro plan feature.

#Features reference

#Pre-Process: Order Data

• What it does - a background cron job indexes order data into ShipEasy's custom database columns. Advanced columns like "# SKUs in order" and revenue calculations depend on this index being current.
• When to use it - enable after installation and leave it running. On a fresh install with many historical orders, the initial index may take several minutes to a few days depending on order count and batch size.
• Config path: Stores > Configuration > Moogento > ShipEasy > Pre-Process: Order Data (moogento_shipeasy/indexer_order/cron_job_status)
• Key settings:
  • Orders indexed each run - default 500. Increase for faster initial indexing on a powerful server; reduce if the server is under load.
  • Skip archived orders - default Yes. Significantly reduces processing time on Adobe Commerce installations where the archive module is active.
  • Skip orders older than X days - default 1. Set to blank (no limit) for a full historical import; set to 30-90 for active stores that only need recent data indexed.
  • A Manual button processes the last 50 orders immediately without waiting for cron.

#Orders Page: Action Menu Options

• What it does - controls which bulk-action buttons appear in the orders-grid toolbar. You can hide actions your team doesn't use to keep the interface clean.
• When to use it - hide unused actions (e.g. hide Invoice if your accounting system invoices automatically).
• Config path: Stores > Configuration > Moogento > ShipEasy > Orders Page: Action Menu Options (moogento_shipeasy/actionmenuoptions/*)
• Toggleable actions: Invoice, Ship, Invoice & Ship, Update Status, Set OrderTag, Set OrderTag.2, Set OrderTag.Printed, Update Priority, Update Shiprule.

#Orders Page: 1-Click Emails & Comments Templates

• What it does - pre-fill the subject and body used when your team sends a quick email or adds an order comment from the grid. Supports tokens: {customer-name}, {order-id}, {ordered-skus}, {sku-name}, {ordered-product-names}, {website-url}, {website-name}.
• When to use it - set once, then your warehouse or support team can send on-brand messages in one click without typing.
• Config path: Stores > Configuration > Moogento > ShipEasy > Orders Page: 1-Click Emails & Comments Templates (moogento_shipeasy/emailsandcommentstemplates/*)

#Process: Scan (Pro)

• What it does - shows a barcode-scan button on the orders page. Clicking it opens a scan interface where warehouse staff can scan order IDs, product barcodes, or tracking numbers to process orders without touching a mouse.
• When to use it - ideal for warehouse pick-and-pack stations where speed and hands-free operation matter.
• Config path: Stores > Configuration > Moogento > ShipEasy > Process: Scan (moogento_shipeasy/process_scan/show_process_scan)

#Order Detail: Product Grid

• What it does - adds product thumbnail images to the order detail product table, so staff can visually confirm the items in the order.
• When to use it - enable for warehouses where visual product recognition reduces pick errors.
• Config path: Stores > Configuration > Moogento > ShipEasy > Order Detail: Product Grid (moogento_shipeasy/product_grid/show_product_images)

#Integration: Zendesk

• What it does - connects ShipEasy to your Zendesk account so you can create a support ticket from any order row in one click. The ticket form pre-fills with order and customer data.
• When to use it - useful for support teams who handle customer queries by searching orders and need to open tickets without switching between tabs.
• Config path: Stores > Configuration > Moogento > ShipEasy > Integration: Zendesk (moogento_shipeasy/zendesk_integration/*)
• Requirements: Growth or Pro Contact column. After saving Zendesk credentials, enable the Contact > Zendesk column in the Orders Page: Columns to see the Zendesk icon on each order row.

#Advanced configuration

#Override Magento's status-change restrictions

#What it does

Magento normally prevents certain status transitions (for example, cancelling a Completed order). The Allow changing status even where Magento logic doesn't allow it? toggle in the General group lifts those guards.

#Setup

1. Go to Stores > Configuration > Moogento > ShipEasy > General.
2. Set Allow changing status even where Magento logic doesn't allow it? = Yes.
3. Save config.

Technical path: moogento_shipeasy/general/allow_se_changing_status

#Notes

• Use with care. Orders that have been force-transitioned outside normal Magento state flows may behave unexpectedly if you later try to invoice, ship, or refund them through standard Magento tools.
• The Allow 'sE: Ship' without Invoice option (moogento_shipeasy/general/allow_complete_without_invoice) is a related toggle that lets you mark an order as shipped before an invoice exists.

#Define which status means "Shipped"

#What it does

ShipEasy fires a "shipped" event whenever it moves an order to the status you designate as Shipped. This is used to trigger external integrations (Amazon, Etsy, 3PL services) via Magento's event system.

#Setup

1. Go to Stores > Configuration > Moogento > ShipEasy > General.
2. Set Which status = Shipped? to the order status your store uses to represent a shipped order (default: Complete).
3. Save config.

Technical path: moogento_shipeasy/general/define_shipped_status

#Suppress order status comments

#What it does

By default, Magento and ShipEasy both add a comment to order history every time the status changes. These can clutter the order comment thread. The General group offers three suppression options:

• Disable ShipEasy status-change comments? (moogento_shipeasy/general/disable_szy_order_status_comment)
• Disable Magento status-change comments? (moogento_shipeasy/general/disable_magento_order_status_comment) - Pro plan
• Disable M2Epro order comments? (moogento_shipeasy/general/disable_m2epro_order_comment) - Pro plan
• Allow deletion of order status comments? (moogento_shipeasy/general/enable_delete_order_status_comment) - adds a delete button to individual comments on order/invoice/shipment/credit memo pages; Pro plan

#Setup

1. Go to Stores > Configuration > Moogento > ShipEasy > General.
2. Toggle the options appropriate for your store.
3. Save config.

#Other pages in this guide

• ShipEasy overview, installation and FAQs
• ShipEasy: Tips, Command Line and Troubleshooting