Running Scope? Keep it, or move on.
You can keep the system you run today and add FreighAI around it, or move on from it and let FreighAI be your main system. Start with pricing and operations either way, and add the rest when you are ready.
Scope is the freight forwarding software made by Riege Software, and it covers a lot of ground: the air and ocean file from quoting to billing, airline and ocean carrier messaging, customs filing, invoicing between branches, and Connect. Most teams keep all of it and put FreighAI around the mail. Some decide the file itself should move. This page covers both.
Every email your company receives is read, understood and turned into a task for the right person, with the answer already drafted. Your team approves. Nobody lives in the inbox any more.
- 01There are two ways in, and this page covers both. Keep Scope and add FreighAI around it, or move on from Scope and let FreighAI be your main system.
- 02Most teams start with the first. Scope holds the file: the air and ocean shipment from quoting to billing, the e-AWB, airline and ocean carrier messaging, customs filing, invoicing between branches and Connect.
- 03Scope already has email, and this page says so first. Riege writes that the email function is integrated into the Scope electronic file, so offers, booking confirmations, bills of lading and document packs go out from inside the file.
- 04Scope already has AI as well. Riege's May 2022 announcement describes the traide.ai tariff classification tool inside the Scope customs tariff module, which finds a suitable tariff number from a description of goods and flags numbers that are out of date.
- 05So the distinction is direction. Scope's mail leaves a file. The work that hurts is the mail that arrives before any file exists to send from. Watching every company mailbox, turning an incoming email into a task for the right department, reading an attachment into an enquiry, and drafting the counter-offer for approval are not described in Scope’s published material, checked September 2026.
- 06FreighAI works that inbox instead of your people. What lands on a desk is a task already written, with a name on it. You keep your own carrier accounts and negotiated rates. FreighAI never sits between you and your carrier relationship. There is no live Scope connector and this page does not invent one. We scope the first workflow, integration requirements and implementation plan with your team.
Scope already carries more than most systems of record
Start with the air freight side. The file runs from quoting to booking and shipment creation to billing. The e-AWB is generated automatically once a shipment is complete and can be transmitted to the airline on its own. Messages move between Scope and the airlines through the Riege Cargo Community System, and where an airline offers it a booking can be made straight from Scope. Documents print automatically and shipment status comes back by itself.
The ocean side is built the same way. An offer can be sent by email directly from Scope to a client. Bookings become transport orders and Scope creates the documents that go with them. Ocean Carrier Messaging gives visibility down to container level, with direct communication to INTTRA, Infor Nexus and CargoSmart.
Customs is where Scope is unusually deep. Riege publishes customs software for the United States, Germany, the Netherlands and Switzerland. The US AES module creates export declarations and transmits the Electronic Export Information, and the Importer Security Filing application files ISF entries with direct integration to CBP. The published catalogue also names ATLAS, the Belastingdienst, Swiss customs and NetCHB.
Around that sits an integration catalogue more specific than most vendors publish: DAKOSY, Portbase and DBH for port messages, EDIfly and CHAMP for airline traffic, Webcargo and TACT for air rates, Chain.io for file formats, and accounting connections such as QuickBooks, DATEV and Sage. Denied party checks run on demand, with sanctions screening through AEB. That is a serious system of record.
Every capability above starts from a file. Somebody has to have read something, decided what it was, and opened the record. Before that, the work is mail. So look at one ordinary morning in pricing@, operations@, tracking@ and accounts@:
- An air enquiry arrives with dimensions in a PDF and no gross weight. There is no Scope file yet, so nothing to send an offer from.
- Four agents are emailed for a lane you do not hold, and somebody has to remember which two never replied.
- A customer who never logs into Connect asks where the cargo is, on a thread with four replies already.
- A carrier bill lands in accounts@ and a person matches every airway bill back to its job.
None of that is a criticism of Scope. It describes where the work sits. Scope sends mail out of a file that exists. The work that hurts arrives before any file does.
Enquiries, agent rate replies, booking confirmations and carrier bills arrive here first.
Reads the thread, chases the agent, drafts the reply and hands a finished task to the right person.
The shipment, the e-AWB and carrier messages, the declaration, the invoice and Connect.
What would change around the Scope file?
FreighAI takes over that inbox. It watches every company mailbox, pricing, operations, tracking and accounts, and follows each conversation from start to finish. It works out what each email is and what it needs, then takes the action that message calls for. Follow-ups, chasers and reminders happen on their own, on the same conversation. Your people work in FreighAI, not in the inbox.
The email is only the start. The real time goes on what comes after it. Find the rate on the carrier’s site. Check the tracking in another tab. Open the TMS for the job. Look up what you charged this customer last time. Forward it to operations and wait. Chase the agent, or forget to. FreighAI does all of that itself. It pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system. It chases what has not come back. It passes the work from pricing to operations to accounts, with the email and everything it found attached. Nobody forwards it. Nobody re-keys it. Nobody asks for an update. Then it puts the finished piece in front of the right person, with the reply already written.
Your people work in FreighAI. Not in the inbox. Not in five browser tabs. Scope keeps the file, the messaging, the filing and the invoicing. That shows up as four changes to the way an enquiry moves:
- It is read where it lands, not after somebody opens a record. Spots what is missing in an enquiry and drafts the email asking for it.
- Emails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply.
- Suggests a price from what that customer paid on that lane before, within your margin rules. When the customer pushes back on price, a counter-offer is drafted and waits for approval.
- Work passes from pricing to operations to accounts with the email and everything it found attached. Nobody forwards it, re-keys it or asks for an update.
need DHL quote Gurugram → Ajman, 72kg, by Friday. express.
packing list attached. urgent pls 🙏
Pls quote for shipment as below. Confirmed pkg dims attached, IEC docs to follow…
One screen. The enquiries with no Scope file behind them.
These are the messages that arrive before anything exists to send an offer from. An enquiry with the weight missing. An agent's rate reply with the charges typed into the mail. Each becomes a task with a name on it.
- Every mailbox, not oneWatches every company mailbox, pricing, operations, tracking and accounts, and follows each conversation from start to finish.
- The attachment is read tooReads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans.
- Your team decidesYour team approves every reply before it sends.
Keep Scope, or move on.
You can keep the system you run today and add FreighAI around it, or move on from it and let FreighAI be your main system. Start with pricing and operations either way, and add the rest when you are ready.
Keep Scope. Add FreighAI around it.
This is the door most Scope teams take, and the rest of this page argues it. Scope keeps the file, the messaging and the filing. FreighAI works the mail that arrives before a file exists.
- Scope keeps the air and ocean file from quoting to billing, its documents and its invoicing.
- The customs filing does not move. The AES declaration, the ISF entry and the tariff number stay in Scope.
- FreighAI takes the mail that arrives first. The enquiry with no weight, the agent’s rate reply, the carrier bill.
- Your team approves every reply. The agreed hand-off carries the won job to Scope.
Move on from Scope. FreighAI becomes your main system.
The other door. You work in FreighAI and let Scope go. Start with pricing and operations, and bring the rest across when you are ready.
- Enquiries and the quotes that follow them.
- Jobs, once a quote is won.
- Tracking replies to customers who email you.
- Carrier bills, matched line by line.
- Payment follow-ups and chasers.
- Your accounts. Finance runs inside FreighAI.
- Customs filing. FreighAI files nothing. The AES declaration, the ISF entry and the tariff number need a customs system or a broker.
- Airline and ocean carrier messaging. The e-AWB and the container feeds still have to come from somewhere.
- A portal like Connect, if your customers and agents log in to look rather than emailing you.
- Denied party and sanctions screening.
- Statutory books, and invoicing between your own branches.
- Air rate feeds such as Webcargo and TACT, if you price air from them inside Scope.
- How long have you had Scope?
A file your team has built for years is worth keeping. One bought recently and still being set up is a different decision.
- Does your team work in Scope, or around it?
Watch one ordinary morning. If the day happens in the inbox and Scope gets updated afterwards, cost the second door.
- What would you lose?
List what only Scope holds: the customs filing, the airline and carrier messaging, Connect. Each one needs a home first.
- What do your contract and your data say?
Ask Riege when the agreement renews and how you get your own history out. Ask. Do not assume.
On its own, FreighAI runs your enquiries, quotes, jobs, tracking replies, carrier bills, payment follow-ups and your accounts. FreighAI does not file customs declarations. It treats customs as a service provider or agent, and your team adds and updates the filing details by hand.
Which parts of FreighAI might a Scope team use?
Quotation Agent
The enquiry arrives by email or WhatsApp, before an offer exists anywhere. FreighAI spots what is missing in an enquiry and drafts the email asking for it. It emails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply. When the customer pushes back on price, a counter-offer is drafted and waits for approval. Quotes expire on their own and can be revived if you want. Scope stays where the offer and the shipment are recorded once the answer is agreed.
Booking and Job Orders Agent
A won quote becomes a job on its own, fully filled in. A booking confirmation that lands in operations@ becomes a task for whoever owns the thread rather than something a person reads and re-keys.
Tracking Agent
FreighAI answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval. Connect already serves every customer and agent willing to log in and look. This covers the ones who will only ever write you an email.
Invoice Reconciliation
FreighAI reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked. Scope keeps the invoicing, the branch-to-branch posting and the accounting connection. Whether an approved match returns to Scope is decided in technical scope.
Start with the mail that has no Scope file behind it yet. Nobody needs every FreighAI area for a first workflow.
What happens to one enquiry
Quotation is the first workflow here, because the enquiry is the clearest case of work that arrives before a Scope file can exist.
An enquiry arrives. FreighAI reads it, notices the weight is missing and asks for it. It pulls your rate cards, checks the carrier for a live rate, and emails your agents for the lanes you do not hold, then chases them until they reply. It drafts the quote with your margin rules and what that customer paid on that lane last time. Your pricer approves and it goes. It follows up. When the customer pushes back, the counter-offer is already drafted. When the quote is old, it expires. When it is won, the job is created.
Where the rate can be fetched without waiting on a person — a carrier API, a portal read in the background, or your own uploaded rate cards — a priced quote goes out in 10–15 minutes instead of 1–2 hours. That holds for ocean and air just as it does for express; the mode does not change it. Where a lane has to be priced by another agent or over the phone, the wait belongs to whoever is answering — not to the software. FreighAI still writes the RFQ, chases the reply, and turns whatever comes back into a priced, margin-checked quote the moment it lands.
Everything right of the approval belongs to Scope, and this page claims nothing about how the result gets there. We scope the first workflow, integration requirements and implementation plan with your team.
need DHL quote Gurugram → Ajman, 72kg, by Friday. urgent pls 🙏
Hi Marco — DHL Express, AED 425 + AED 35 handling. ETA Thu·18:00, valid 24h. PDF attached.
- 01Enquiry emailAir or ocean, into pricing@ or WhatsApp
- 02Reads itAsks for what the attachment does not give
- 03RatesYour rate cards, your carrier account, your agents chased
- 04Drafted quoteWritten against the thread it arrived on
- GATEYour pricer approves
- 06Follow-upPlus the counter-offer when the price is pushed back
- 07Scope shipmentThe file, its documents and its billing
- 08Scope customsThe AES or ISF filing, exactly where it is now
At Infinity Logistics, average response time fell from more than 60 minutes to about 15 minutes, and the win rate rose from 35% to 73%. Those are one customer's attributed results, not a promise to every business.
What stays in Scope, what FreighAI adds and what has to be scoped?
| Area | Stays in Scope | FreighAI adds | Decision required |
|---|---|---|---|
| The shipment file | The air and ocean file from quoting to billing, with transport orders | The enquiry before a file exists, and the mail that arrives after it | How does an approved task reach the Scope file? |
| Carrier messaging | The e-AWB, airline messaging through the Riege Cargo Community System, and Ocean Carrier Messaging to INTTRA, Infor Nexus and CargoSmart | Answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval. For the customer who writes rather than logs in | Whose status is quoted back, and who approves it? |
| Customs and tariffs | Customs software for four countries, the AES declaration, ISF filing into CBP, and traide.ai tariff classification | Nothing. Filing, duty and classification stay in Scope. What changes is the mail chasing the documents a declaration waits on | What does the filing desk wait on today? |
| Invoicing and accounting | Invoicing, branch-to-branch posting and accounting connections including QuickBooks, DATEV and Sage | Reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked. | Where does an approved match land? |
| Rates and tariffs | Air rate feeds from Webcargo, and air cargo tariffs and schedules from TACT | Emails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply. Suggests a price from what that customer paid on that lane before, within your margin rules. | Which rate sources should the demonstration cover? |
| The enquiry thread | Offers sent by email directly from Scope to a client, once a file exists | Drafts the quote and the counter-offer and follows up on the same thread. Reading an incoming enquiry email into a quotation is not described in Scope’s published material, checked September 2026 | What starts the workflow, and which follow-ups move? |
| The email function integrated into the electronic file, sending offers, confirmations, pre-alerts and documents outward | Mail arriving at the company, worked out, assigned and drafted. Watching every mailbox and turning what arrives into a task are not described in Scope’s published material, checked September 2026 | Which mailboxes does FreighAI watch, and in whose name do replies go? | |
| Documents and access | Documents printed automatically, and Connect for customers and agents | Reads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans. The attachment is read with its thread | Which documents may FreighAI open? |
| Connections between the two | Riege's published integration catalogue, including Chain.io, which Riege says processes any file format such as EDI, XML or CSV | Nothing is claimed. No Scope connector is live. We scope the first workflow, integration requirements and implementation plan with your team. | Which objects, which direction, whose credentials? |
- The shipment file
- Stays in Scope
- The air and ocean file from quoting to billing, with transport orders
- FreighAI adds
- The enquiry before a file exists, and the mail that arrives after it
- Decision required
- How does an approved task reach the Scope file?
- Carrier messaging
- Stays in Scope
- The e-AWB, airline messaging through the Riege Cargo Community System, and Ocean Carrier Messaging to INTTRA, Infor Nexus and CargoSmart
- FreighAI adds
- Answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval. For the customer who writes rather than logs in
- Decision required
- Whose status is quoted back, and who approves it?
- Customs and tariffs
- Stays in Scope
- Customs software for four countries, the AES declaration, ISF filing into CBP, and traide.ai tariff classification
- FreighAI adds
- Nothing. Filing, duty and classification stay in Scope. What changes is the mail chasing the documents a declaration waits on
- Decision required
- What does the filing desk wait on today?
- Invoicing and accounting
- Stays in Scope
- Invoicing, branch-to-branch posting and accounting connections including QuickBooks, DATEV and Sage
- FreighAI adds
- Reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked.
- Decision required
- Where does an approved match land?
- Rates and tariffs
- Stays in Scope
- Air rate feeds from Webcargo, and air cargo tariffs and schedules from TACT
- FreighAI adds
- Emails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply. Suggests a price from what that customer paid on that lane before, within your margin rules.
- Decision required
- Which rate sources should the demonstration cover?
- The enquiry thread
- Stays in Scope
- Offers sent by email directly from Scope to a client, once a file exists
- FreighAI adds
- Drafts the quote and the counter-offer and follows up on the same thread. Reading an incoming enquiry email into a quotation is not described in Scope’s published material, checked September 2026
- Decision required
- What starts the workflow, and which follow-ups move?
- Email
- Stays in Scope
- The email function integrated into the electronic file, sending offers, confirmations, pre-alerts and documents outward
- FreighAI adds
- Mail arriving at the company, worked out, assigned and drafted. Watching every mailbox and turning what arrives into a task are not described in Scope’s published material, checked September 2026
- Decision required
- Which mailboxes does FreighAI watch, and in whose name do replies go?
- Documents and access
- Stays in Scope
- Documents printed automatically, and Connect for customers and agents
- FreighAI adds
- Reads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans. The attachment is read with its thread
- Decision required
- Which documents may FreighAI open?
- Connections between the two
- Stays in Scope
- Riege's published integration catalogue, including Chain.io, which Riege says processes any file format such as EDI, XML or CSV
- FreighAI adds
- Nothing is claimed. No Scope connector is live. We scope the first workflow, integration requirements and implementation plan with your team.
- Decision required
- Which objects, which direction, whose credentials?
Read this as the outline of a boundary conversation, not a list of Scope connections. One word does double duty here: Scope with a capital S is Riege's product, and scoping is the conversation about where the line falls.
What Scope does that FreighAI does not
A page that only flatters one side is not worth reading. Here is the honest list, from Riege's own pages.
- Customs filing in four named countries, with AES declarations and ISF entries going straight into CBP. FreighAI files nothing.
- Airline messaging through Riege's own Cargo Community System, with the e-AWB transmitted automatically.
- Ocean carrier messaging to INTTRA, Infor Nexus and CargoSmart, down to container level.
- Branch-to-branch invoicing, where one office's outgoing invoice becomes the other's incoming invoice without anyone posting it twice.
- Denied party checks on demand, and an integration catalogue unusually specific about message types.
- Real AI in tariff classification through traide.ai, finding a tariff number from a description of goods.
Most of that sits on a line FreighAI already draws for itself. Customs filing and duty lookup stay in the customer's system, and so do statutory books, self-service portals and full warehouse and fleet management.
The objections we hear most
“Scope already sends email from the shipment file. What is left to add?”
A direction. Riege describes offers, bills of lading and document packs going out from the electronic file, and all of that starts with a file somebody has already opened. FreighAI works the other way: the enquiry, the rate reply and the carrier bill that arrive before anyone has opened anything. Watching every mailbox and turning what arrives into a task are not described in Scope’s published material, checked September 2026.
“Scope already has AI in customs. Why would we buy more AI?”
Because they are pointed at different problems. Riege's published AI is the traide.ai tariff classification tool in the customs tariff module. It reads a description of goods and finds a suitable tariff number. FreighAI does not do that. It reads your pricing, operations, tracking and accounts mail and turns it into finished tasks. One classifies a commodity. The other works an inbox.
“Our customs desk files in four countries. Does any of this touch that?”
No. Filing and duty lookup stay in the system you run, and here that means Scope. The AES declaration, the ISF entry and the tariff number stay where they are. What FreighAI touches is the mail either side of a filing, such as the packing list you are still waiting on.
“Are you asking us to move off Scope?”
Only if you want to. You can keep the system you run today and add FreighAI around it, or move on from it and let FreighAI be your main system. Start with pricing and operations either way, and add the rest when you are ready. On its own, FreighAI runs your enquiries, quotes, jobs, tracking replies, carrier bills, payment follow-ups and your accounts. Moving off a system that files customs in four countries is a big decision, and the two doors above set out how to weigh it.
“Is there a finished Scope connector?”
No, and no universal claim is made. Riege publishes a specific integration catalogue and names Chain.io as a route for file formats such as EDI, XML and CSV. A catalogue is not a finished connection. We scope the first workflow, integration requirements and implementation plan with your team.
“How quickly could we be live?”
That depends on the workflow, the mailbox access, the sample threads and what any hand-off has to support. FreighAI publishes no fixed pilot length and no go-live promise. A number invented before the scope exists is worth nothing.
Common questions
Can FreighAI be my main system instead of Scope?
Yes, if that is what you want. On its own, FreighAI runs your enquiries, quotes, jobs, tracking replies, carrier bills, payment follow-ups and your accounts. FreighAI does not file customs declarations. It treats customs as a service provider or agent, and your team adds and updates the filing details by hand. The airline and carrier messaging, Connect and the four countries of customs filing are things Scope holds today, so give each one a home before you move.
Do we have to move data out of Scope?
Not automatically. A first workflow may need only selected current context, and it may run beside Scope without reading anything from it. Anything that has to move is named and justified during scope.
Can FreighAI write back into Scope?
That answer comes from the confirmed scope for the chosen workflow. Riege's published catalogue, and Chain.io in particular, is where the question starts. Until it is agreed and written down, assume a person carries the approved result across.
Which workflow should a Scope team start with?
Start where work arrives by email or WhatsApp, passes between people, and waits for somebody to remember. On most Scope sites that is the enquiry with no file behind it yet. For some it is the carrier bill.
What happens to Connect?
Nothing. Connect stays as it is, and customers and agents who log in keep doing that. FreighAI answers the customer who never logs in and writes to you instead, on the thread they wrote on.
Does a person still approve every reply?
Yes. Your team approves every reply before it sends. Your team approves. They do not compose, forward, file or chase. The reply goes out in their name. Chasing, tracking checks, quote expiry and follow-ups run on their own. Nobody has to remember. The supervision rules for each workflow are shown during the demonstration.
Do our agents and customers have to change how they contact us?
No, and that is the point. They keep writing to the same addresses, with the same attachments. Nobody gives up email. Your own people simply stop living in it. FreighAI talks to carriers, portals, your TMS and your accounting system itself. Nobody hops between websites to put an answer together.
- Riege Software — Scope: freight forwarding software for air and ocean, customs software for four countries, and airline messagingverified 2026-09-03
- Scope — Freight Forwarding Software: offer to booking to invoicing, shipment status and milestones, denied party checks on demand, US AES and ISF integratedverified 2026-09-03
- Scope Air Freight — the e-AWB generated automatically once a shipment is complete, airline messages through the Riege Cargo Community System, documents printed automatically, Connect for customers and agents, and the email function integrated into the electronic fileverified 2026-09-03
- Scope Sea Freight — offers sent by email directly to a client, bookings entered as transport orders, and Ocean Carrier Messaging with container-level tracking to INTTRA, Infor Nexus and CargoSmartverified 2026-09-03
- Scope Customs — for the US, Germany, the Netherlands and Switzerland, with the AES module transmitting Electronic Export Information and the ISF application filing entries directly into CBPverified 2026-09-03
- Scope Airline Messaging — automatic message exchange with airlines through the Riege Cargo Community System, bookings made from Scope where an airline offers it, and status updated in the shipment monitorverified 2026-09-03
- Riege — Freight Forwarding industry page: order processing, access to third party systems, and paperless exchange of documentsverified 2026-09-03
- Riege — Integrations and partners: DAKOSY, Portbase, DBH, INTTRA, EDIfly, Webcargo, TACT, Chain.io and CHAMP for freight, ATLAS, CBP, the Belastingdienst, Swiss customs and NetCHB for customs, QuickBooks, DATEV and Sage for accounting, and AEB for sanctions screeningverified 2026-09-03
- Riege Software — Company: no founding year, headquarters or country count is stated, so none is asserted hereverified 2026-09-03
- Riege Software press release, 16 May 2022 — the traide.ai tariff classification tool in the Scope customs tariff module, finding a tariff number from a description of goods within secondsverified 2026-09-03
- Infinity Logistics customer reference, 15 May 2026 — response time and win rateverified 2026-08-31
No Riege customer or reference company is named here. The systems named above are the ones Riege publishes as integrations, data feeds, filing channels or embedded tools. Riege's operator, customer and branch counts are not repeated, and no founding year or ownership is asserted, because the company page states none. The Scope Connect URL returned a 404 on 3 September 2026.
Bring one thread that has no Scope file yet
Pick a morning from last week. An enquiry with the weight missing, an agent's rate reply typed into the mail, or a carrier bill nobody has matched. We will show what FreighAI would have read, drafted and assigned, and what stays in Scope.