What Needs Doing Next: The Action Center and Automations

Every busy gun shop has the same problem by mid-afternoon. There are orders waiting to ship, transfers waiting on paperwork, layaways that haven’t seen a payment in a month, and holds nobody remembers placing. WooCommerce’s order list can show you one status at a time, so finding all of that means clicking through filter after filter and keeping the rest in your head, or on a sticky note by the register.

The Action Center and Automations are our answer. The Action Center turns your orders into shared work queues, so anyone on staff can open one screen and see what needs doing next. Automations handle the routine follow-up those queues reveal, like reminding a customer their layaway is past due, so your staff can spend their time on the work that actually needs a person. We haven’t seen anything like it in other firearms retail software.

One screen for everything that needs a person

The Action Center sits right under Dashboard in your admin menu. Across the top is a row of saved views, each one a queue with a live count beside its name. A new store starts with a sensible set:

• Needs action for orders that are paid or arrived and waiting on staff.
• Ship queue for everything that has to go out the door.
• Holds for POS holds, raffle holds and partial payments.
• Layaways, Past due layaways and Stalled layaways for the plans that need a phone call.
• Untagged active for orders nobody has picked up yet.

Click a view and you get its orders, oldest first by default, with the age of each one colored amber after a week and red after two. A summary strip above the table shows how many orders are in the view, how many are older than a week and, for layaway queues, how much is still owed. Views are shared, so the whole team works from the same lists, and anyone can keep a few personal views marked “Only me”. Every view has its own link, which makes it easy to bookmark the ship queue on the shipping station or put Needs action on a wall screen with auto-refresh turned on.

Views built around how your shop works

Each view is a set of rules that all have to match, and you build them with buttons rather than code:

• Status can be all active orders, only certain statuses, or everything except some. Custom statuses from other plugins show up automatically.
• Workflow tags can require any of a set of tags, all of them, none of them, or no tags at all.
• Age limits a view to orders older or newer than a number of days.
• Source separates POS sales, website orders and GunBroker orders.
• Layaway standing finds plans past their term, plans with no payment in a set number of days, or plans whose term ends soon, and can filter by how much has been paid.

Workflow tags are labels your staff define, with their own colors, like “waiting on customer”, “needs call” or “FFL received”. They sit on top of WooCommerce’s order statuses instead of replacing them, so you can track where an order really is without breaking the status flow your register, emails and reports depend on.

You also choose which columns each view shows. A ship queue might want items and source, while a layaway queue wants percent paid, last payment and term end date. From the table, staff can tag orders, add notes and change statuses one at a time or in bulk, and each change is checked after it’s saved, so a status change that didn’t take shows up as a problem instead of quietly disappearing. Any view can also be exported to CSV, every page of it, for a call list or the end-of-month review.

Layaways that can’t slip through

Layaways are where we saw the biggest gap. On one high-volume store we work with, the existing overdue reminders depended on a scheduled next-payment date that only about one plan in six actually had, so most late plans never triggered a reminder at all. When we looked at the same store’s data, about fifty plans hadn’t had a payment in over a month and sixteen were already past their term.

The Action Center works from facts every plan has: when it started, how long the term is and when the last payment came in. That’s why the default views include both Past due layaways, for plans past their term, and Stalled layaways, for plans with no payment in 30 days. Paid-off plans waiting on pickup never show up as late.

Stores that set a payment schedule, such as a percentage due by certain days, get more. The Action Center flags every plan that missed a milestone and shows how many days late it is and the amount needed to catch up, and a Most overdue sort puts the plans furthest behind at the top. If a plan’s balance can’t be confirmed, it goes into a review list with the reason instead of being counted as current or late.

Automations: when this happens, do that

Once you can see the work, a lot of it turns out to be the same steps every time. Automations let you write those steps down once as a rule. Each one reads top to bottom, with no flowchart to wire up:

• When something happens, like an order changing status, a tag being added, a layaway payment coming in, or a layaway going a week past its term.
• If the conditions you set are true, like a balance still owed, an email on file, or no “waiting on customer” tag yet.
• Then take one or more actions, in order.
• Else do something different, so the same rule can email the customers it can reach and tag the rest for a phone call.

Triggers come in two kinds. Event triggers run as soon as something happens: a new order, a status change, a tag added or removed, a note, or a layaway being created, paid, paid off or cancelled. Time triggers run in a daily sweep and catch the things that happen by not happening, like a layaway with no payment in 30 days or an order sitting in Ready for Pickup for a week. A time trigger fires once per order by default and ignores orders created before the rule existed, so turning on a new rule doesn’t send a flood of emails about years-old orders.

The actions cover most of the follow-up a shop does by hand:

• Send an email to the customer, to staff, or to any address, with placeholders like the customer’s first name, the layaway balance and the term end date filled in.
• Send a webhook to your CRM or texting service, with the order, customer and layaway details you choose. Deliveries can be signed so the receiving service knows they came from you, and failed ones are retried automatically.
• Change the order’s status, add or remove a tag, or add a note to the order.
• Wait for up to 30 days before the next step. Any conditions after the wait are checked against the order as it is by then, so a rule can skip the reminder for a customer who paid in the meantime.

Put together, a rule can read like this: when a layaway is seven days past its term, if a balance is still owed and the customer has an email address, send them a friendly note with their balance and the shop’s phone number and tag the order “waiting on customer”. Otherwise, tag it “needs call”. Every one of those orders then shows up in the right Action Center queue without anyone sorting them.

The same pattern works for pickups. The rule below emails customers whose order has sat in Arrived for a week, tags anyone without an email address for a call, then waits three days and flags any order that still hasn’t been picked up.

Built to be trusted with your customers

A rule that emails customers has to be easy to check and hard to get wrong, so we put most of our effort there.

• Test before it goes live. Pick any order and run the rule against it as a dry run. You’ll see which branch it would take and the exact email or webhook it would send, without anything actually going out.
• Every run is logged. The run log shows each run and each step, like “Sent webhook, 200” or “Status changed to Processing”, with failures highlighted, and keeps 90 days of history.
• No loops. A rule can’t set itself off, chains of rules triggering each other stop after a few steps, and any one rule can only run on an order so many times a day. Anything that hits a limit is logged and flagged.
• Fresh data, every time. Conditions are checked when the rule runs, not when it was triggered, so a rule skips an order that has already moved on.
• Nothing happens twice. If a run is interrupted partway through, it won’t repeat steps it already finished. An administrator sees what happened and decides how to continue.
• The right people can edit. Only administrators can create or change rules. Shop managers can see every rule and the run log.

The Automations page also lists the automations that already run outside it, like WooCommerce’s own emails, layaway reminder emails and webhooks to outside services, each with a link to where it’s managed. Before you add a rule that emails customers, you can see everything else that already does, which is the easiest way to avoid sending someone the same reminder twice.

Getting it in your shop

The Action Center and Automations are part of MFS Exchange. When we set them up for a shop, we start with the default views, add the workflow tags your staff already use in their heads, and turn on a few rules for the follow-up you do most often. If you’d like to see them on your own orders, book a time with us.