How to Automate ePS Radius

The packaging ERP many converters still call EFI is now ePS Radius, sold by eProductivity Software. Its estimating, order management and scheduling already run the plant. Getting what it knows onto the floor, into a shared sheet or in front of a customer is a person's morning, until WebRun starts opening those screens instead.

Every job starts as an estimate and ends on a pallet

ePS Radius is the system a packaging converter is run from, and plenty of the plants running it still call it EFI. Electronics For Imaging sold that software business to Symphony Technology Group at the end of 2021, and it trades now as eProductivity Software, shortened to ePS, while EFI carried on with inkjet presses. The screens did not change. The badge on them did.

Radius was built for converters in folding carton, labels and flexible packaging, and it works outward from the estimate: a quote priced against master estimate logic, a sales order carrying the spec and the promised date, a route through press, die-cut, glue and pack, then a pallet count, a bill of lading and an invoice.

So most of the building passes through it: the estimator, the rep who owns the date, the planner deciding what runs tonight, the tool room, the shift lead, the shipping clerk.

The floor finds out because somebody typed it in

Radius knows what runs tonight. The press crew learns it when someone in the office copies it out of the system and onto the floor.

The run order gets retyped into a message, or printed and taped up. Yesterday's shipments get keyed off the shipping screen into a spreadsheet, then keyed again into a note to the customer with the pallet count, carrier and BOL. Last week's runs get opened job by job to set actual waste beside the estimate.

The quiet ones have no owner at all. A proof that went to a customer eleven days ago and has not come back. A grade of roll stock under its reorder point. A die due for sharpening before Tuesday's job. A spec revised on Thursday afternoon, caught only if somebody opens the right job.

Tonight's run order on the floor The order of jobs on each press, with the longest changeovers ranked so plates, dies and ink are staged before the press stops.
Jobs that slipped, found in the morning Open orders already behind their promised ship date, and specs revised overnight matched to jobs still running the old version.
Reorders and notices drafted, not sent A grade that has dropped below its reorder point, with the order to the mill drafted, and each day's shipment notice written from the pallet count and BOL.

The quote becomes the order without being retyped

A plant that uses it only for order entry is using a corner of what it bought.

Estimating is product specific, with master estimate logic and pre-defined route templates, so routing proved once is reused on every quote after it. Sales order management and accounting sit on the record the estimate became. Purchasing and inventory follow substrate by grade and width against what open orders will consume. Production planning and scheduling place work on real machines, with PrintFlow 4D doing that job across the wider ePS suite, and the Direct Machine Interface bringing back what a press actually produced.

That is the manufacturing problem well covered, and why the product has lasted.

The ceiling is not in what it computes but in where the answer stops. Radius is a system of record read by people with a licence and a reason to open it, and the plant is not sitting in front of it. The crew is at the press, the buyer is in the accounting system the plant pays from, the customer is in their own inbox. A fact that has to arrive somewhere else gets carried there by a person.

Tonight's run order can reach the press before the crew does

Now picture the checking done before the shift, and the answers waiting where they are needed.

The run order for every press posted to the shift channel first thing, the first job of each shift marked. Consecutive jobs needing a plate, ink and die change at once, ranked by how long each takes, so plates and dies are staged while the press is still running the job before. A spec revised overnight matched against jobs still open on the old dieline, before a shift of superseded print gets made.

Then the ones with a date on them. Orders whose stage puts them behind their promised ship date, listed by days behind. Roll stock read by grade and width against its reorder point, with the purchase order already drafted and waiting on a manager. Trim waste set against estimate on every run last week, so the substrate that always overruns stops being an opinion. Proofs sent and never signed, ordered by how close the press date is rather than how long they have sat.

Two of those stop short on purpose. The purchase order is drafted and not sent, the customer email written and left unsent: committing money and speaking to a customer are not reading, they are decisions.

The order file can report itself to the floor

That is a shift's worth of opening screens, done before anyone clocks on. Deciding what to do about a job three days behind is still the planner's call.

WebRun is an AI agent that works a real Chrome browser, signed in as your team is. It opens ePS Radius, reads the sales order, scheduling, inventory, costing and shipping screens, and puts the answer where it is useful: a message to the shift channel, a row in the shared sheet, an email waiting in somebody's drafts.

It works on your schedule in a private environment of your own, a second system in the run is just a second login, and anything that costs money or reaches a customer stays a draft.

The list below shows which screens each run touches.

Questions people ask

We still call it EFI. Is ePS Radius the same system?

Yes. Electronics For Imaging sold the software business at the end of 2021 and it now trades as eProductivity Software, but the estimating, order and scheduling screens are the same ones your team already knows. An agent reads them exactly as a person does.

Will anything be changed inside the ERP itself?

Reading is the default, and most plants keep it that way. If a workflow does put something back, such as a shipment logged against an order, you are told which field it touches up front, and a run can be held to reading only.

Could a reorder go to the mill before anyone has approved it?

No. Roll stock runs draft the purchase order and stop there, then post an alert naming what is low and what was drafted. Sending it stays with whoever signs for spend, and customer email follows the same rule: written, then waiting.

12 ready-made ePS Radius workflows

Each one names the apps it touches and the exact steps it takes. Open one to read what it will do, then turn it on.

ePS Radius Automatic Trim Waste Reporting
Every week, WebRun pulls trim waste and scrap totals from ePS Radius for each completed press run, compares them to the job's estimate, and logs a report to Google Sheets flagging any run that came in over.
ePS RadiusGoogle Sheets
ePS Radius Automatic Spec Revision Alerts
Every hour, WebRun checks ePS Radius for specs revised since the last check, finds any open job still tied to the old version, logs the change, and posts a Slack alert so production confirms the current spec before it runs.
ePS RadiusGoogle SheetsSlack
ePS Radius Automatic Ship Date Risk Alerts
Every morning, WebRun checks ePS Radius for orders whose production stage puts them behind their promised ship date, logs each to a Google Sheet, and posts your team a Slack list ranked by days behind.
ePS RadiusGoogle SheetsSlack
ePS Radius Automatic Roll Stock Reorder Alerts
Every week, WebRun checks roll stock inventory in ePS Radius against its reorder points, drafts a purchase order in QuickBooks for anything running low, and posts your team a Slack alert so a manager can approve it before it goes to the mill.
ePS RadiusQuickBooksSlack
ePS Radius Automatic Repeat Order Reminders
Every week, WebRun reviews order history in ePS Radius, finds customers due for their usual reorder based on past cadence, logs them to a sheet, and drafts a reorder email with their last spec and quantity for you to send.
ePS RadiusGmailGoogle Sheets
ePS Radius Automatic Quality Hold Alerts
Every hour, WebRun checks ePS Radius for any job or lot newly placed on quality hold, logs it to a Google Sheet for your QC record, and posts an alert in Slack so shipping doesn't release it.
ePS RadiusGoogle SheetsSlack
ePS Radius Automatic Press Run Schedule Alerts
Every morning, WebRun opens ePS Radius, pulls the day's press run schedule for each press, and posts your shift supervisors a Slack rundown of what runs next and in what order.
ePS RadiusSlack
ePS Radius Automatic Press Changeover Alerts
Every morning, WebRun reviews the press schedule in ePS Radius for the day, flags back-to-back jobs that need a major ink, plate, or die change, and posts your crew a Slack list of what to stage first.
ePS RadiusSlack
ePS Radius Automatic Shipment Pallet Logging
Every night, WebRun pulls the day's completed shipments from ePS Radius, logs pallet count, carrier, and BOL number to a Google Sheet, and drafts a shipment notice for each customer in Gmail for you to send.
ePS RadiusGoogle SheetsGmail
ePS Radius Automatic Tooling Inventory Alerts
Every morning, WebRun checks ePS Radius for the dies and tooling upcoming press runs need, flags anything overdue for sharpening, damaged, or missing from the tool room, logs it to a sheet, and posts your team a Slack alert.
ePS RadiusGoogle SheetsSlack
ePS Radius Automatic Open Order Reporting
Every Monday, WebRun compiles each customer's open orders from ePS Radius, checks which completed orders haven't been invoiced yet in QuickBooks, and logs a combined backlog report to Google Sheets.
ePS RadiusQuickBooksGoogle Sheets
ePS Radius Automatic Proof Approval Reminders
Every morning, WebRun finds jobs stuck waiting on a customer's artwork proof approval in ePS Radius, drafts a friendly reminder for each one, and leaves it in Gmail for you to review and send.
ePS RadiusGmail

Want one of these running on your own ePS Radius?

Show WebRun the process once and it will run it on schedule, in your own private browser environment.