Who this is for: existing Sage X3 SaaS customers and the IT administrators who look after their printers.
What's involved:
Worth knowing up front: parts of this setup are still manual. As of Sage's July 2026 guidance, the PrinterLogic client on the Sage X3 Print server is installed by hand, and automatic deployment from the Sage partner portal is not yet available. We handle that part with Sage for you.
Sage X3 SaaS runs in Sage's cloud and your printers sit inside your office network. PrinterLogic connects the two, so you don't need a VPN between them.
When you print from Sage X3, the job goes to your Sage X3 Print server. The PrinterLogic client there sends it through a regional PrinterLogic gateway to the service client agent in your office, which passes it to the printer. Your PrinterLogic admin portal is where you set all of this up.
You need three things in place before any configuration begins. Missing one of them is the most common reason a setup stalls.
Have this information ready:
|
Task |
Owner |
Notes |
|---|---|---|
|
Buy the PrinterLogic license |
You |
Held in your company's name |
|
Request printing services from Sage |
EvomatiQ |
Raised with Sage L2 support |
|
Configure the PrinterLogic portal (steps 1 to 3, 5 to 7) |
EvomatiQ or your IT team |
We need portal access if we do it |
|
Install the service client agent at each office (step 4) |
Your IT team |
Runs inside your network; we can guide you on a call |
|
Install the PrinterLogic client on the Sage X3 Print server |
EvomatiQ, with Sage |
Manual for now, done by remote desktop |
|
Create the print destination in Sage X3 |
EvomatiQ or your Sage X3 administrator |
|
|
Test print and sign-off |
Both |
One test per printer |
These seven steps link your office printers to Sage X3 SaaS. Do them in order: each step uses something the previous one created. Menu names appear in bold exactly as they show on screen.
This lets print jobs reach printers behind your company firewall.
https://<your-instance>.printercloud5.com/admin/. Your exact address comes with Sage's confirmation. The printercloud5 part varies by region, so use the address you were given.Folders keep your printers organised by location.
The access code links the PrinterLogic agents to your portal.
Keep this code safe. It never expires, so treat it like a password. Store it in your password manager and share it only with the people installing the agents.
The service client agent is a small application that passes print jobs from the PrinterLogic cloud to your printers. Install it on a machine that can reach the printers at that office. If you have two offices on separate networks, install one agent at each.
msiexec /i PrinterInstallerClient.msi /qn HOMEURL=https://<your-portal-address> AUTHORIZATION_CODE=<your-access-code>
Replace <your-portal-address> with your PrinterLogic portal address and <your-access-code> with the code from step 3.
Refresh the agent in either of two ways: select Refresh configuration from the PrinterLogic icon in the machine's system tray, or select Reauthorize on the service client's General tab.
Within a few seconds the status on the Internal Routing tab should change to online.
Optional: tick Enable SNMP Service on the SNMP tab to see each printer's queue in its Status tab. You can enable SNMP on one service client only.
This step makes sure every Sage X3 Print server Sage creates for you picks up your printers automatically, without anyone repeating the setup.
Use this IP range exactly as shown. Sage specifies it for its Print servers. It is not your office network range, so do not change it.
Repeat this step for each printer.
On the same tab, select Add and tick two items: the gateway for your office's region, and the service client that can reach this printer. We confirm the right gateway for GCC offices during setup.
Select Test to check that both the gateway and the service client are connected.
Two things remain: connecting your Sage X3 Print server to the portal, which we handle with Sage, and telling Sage X3 which printer to use.
The PrinterLogic client must also run on the Sage X3 Print server that Sage hosts for you. For now this is a manual install over remote desktop, using the same command as step 4 with your portal address and access code. Automatic deployment from the Sage partner portal is not yet available, so we arrange it with Sage Support.
What we need from you: your PrinterLogic portal address and the access code from step 3, shared through a secure channel rather than plain email.
Once we confirm the Print server is connected, create a print destination in Sage X3 for each printer.
Most problems trace back to one link in the chain being offline. Work through these checks before contacting us.
|
What you see |
What to check |
|---|---|
|
The printer is missing from the Sage X3 lookup |
In the portal, go to Report > Workstation. Sage X3 Print servers show a username containing |
|
The service client shows offline |
On the agent machine, select Refresh configuration from the system tray, or select Reauthorize on the service client's General tab. Confirm Enable Internal Routing Service is still ticked. |
|
The Test button on the printer's Off-Network tab fails |
Check that the right gateway and service client are both ticked, and that the printer's IP address is reachable from the agent machine. |
|
Jobs leave Sage X3 but nothing prints |
Check the printer's Status tab on its Printer Detail page (needs SNMP, see step 5). |
|
You need more detail |
Open the logs in the service client installation folder on the agent machine. They show the status of the PrinterLogic client and the off-network service. |
Still stuck? Contact us with the printer name, the office, and what the checks above showed.
This setup works well once it is in place, but it has limits you should plan around.
Need help? We can run the whole setup for you, or sit alongside your IT team while they do it. Get in touch with us hello@evomatiq.com.