Marathon fleet card product codes are alphanumeric identifiers assigned to specific fuel grades, vehicle maintenance services, and miscellaneous automotive items that allow fleet managers to control, track, and restrict spending at the point of sale. These codes function as a filter, ensuring that company-issued cards are only used for authorized transactions, thereby preventing unauthorized purchases and simplifying accounting reconciliation.
Understanding the Role of Product Codes in Fleet Management
In the context of commercial fleet operations, controlling variable costs—specifically fuel and maintenance—is a primary objective for profitability. Marathon fleet cards operate on a sophisticated processing network that recognizes individual line items during a transaction. Unlike a standard consumer credit card, which typically reports a single "fuel" or "service station" transaction, a fleet card utilizes product codes to break down the basket of goods at the register.
When a driver swipes their Marathon fleet card at a terminal, the card network communicates with the point-of-sale (POS) system. The system queries the product codes associated with the items being purchased. If the specific product code for "Premium Gasoline" or "Car Wash" is restricted on that driver's card profile, the transaction will be declined immediately. This automated enforcement reduces the administrative burden on fleet managers, who no longer need to manually review receipts for every individual purchase to identify outliers or non-compliant spending.
The Technical Mechanism of Authorization
The authorization process for fleet card product codes occurs in milliseconds. When a driver inputs their information, the system performs a multi-layered verification. The process generally follows these stages:
- Terminal Identification: The Marathon terminal identifies the card issuer and the specific fleet account associated with the card.
- Profile Lookup: The system retrieves the unique spending profile assigned to that card or driver. This profile contains "allowed" and "restricted" product categories.
- Transaction Scanning: As items are scanned or selected at the pump/register, the system maps each item to its standardized product code (often known as a Level III data code in payments terminology).
- Validation: The system compares the transaction codes against the pre-set account rules.
- Authorization Response: The network sends an "Approve" or "Decline" signal to the terminal. If a restricted code is detected, the transaction is rejected, providing an instant audit trail that protects the company against misuse.
This granular control is essential for modern fleet management, where managers might authorize fuel for a specific vehicle but want to prevent the purchase of convenience store items, tobacco, or lottery tickets using company funds.
Categorizing Product Codes and Restrictions
Most fleet management programs categorize items to make configuration intuitive for managers. While internal Marathon codes may be proprietary, they generally map to industry-standard categories. Understanding these categories is vital for setting up your fleet management portal correctly.
Fuel Classifications
Fuel product codes are the most frequently used filters. Managers can restrict cards by fuel type to match the specific engine requirements of a vehicle. For example, a card assigned to a diesel-powered heavy truck can be restricted to only authorize "Diesel" product codes, preventing accidental—and expensive—misfueling with gasoline.
Maintenance and Service Codes
Beyond fuel, fleet cards often feature codes for maintenance. These are particularly useful for leasing or service-heavy accounts. These codes distinguish between "Routine Maintenance" (e.g., oil changes, tire rotations) and "Major Repairs" (e.g., transmission work). By enabling or disabling these codes, managers can require prior authorization for major expenditures while allowing routine maintenance to occur seamlessly.
Non-Automotive Items
Many service stations are also convenience stores. A common challenge for fleet managers is "leakage," where employees purchase snacks or other non-essential items on the company tab. By configuring the fleet card to exclude product codes associated with "Merchandise," "Food," or "Tobacco," managers can effectively eliminate these unauthorized expenses at the point of source.
Comparing Transaction Reporting Levels
To understand how product codes function, it is helpful to distinguish between different levels of transaction reporting. Fleet cards generally operate at Level III data standards, which provide the highest degree of visibility.
| Reporting Level | Data Depth | Utility for Fleet Managers |
|---|---|---|
| Level I | Merchant name, date, total amount | Limited; difficult to audit specific items. |
| Level II | Level I + tax amount, merchant zip code | Better for tax compliance; still lacks item detail. |
| Level III | Level II + item quantity, description, product codes | High; allows for precise restriction and granular reporting. |
By utilizing Level III reporting, Marathon fleet cards provide data that enables managers to see not just that a card was used at a specific station, but exactly what was purchased, the unit price, and the total volume of fuel dispensed.
Setting Up and Customizing Your Account
The effectiveness of product codes relies entirely on the initial configuration within the fleet management portal. As a manager in 2026, you should treat the setup of these codes as a living process rather than a one-time task.
1. Define Vehicle Needs: Audit your fleet. Document the specific fuel requirements (Regular, Mid-grade, Premium, Diesel) for every vehicle. 2. Establish Policy: Create a clear written policy for drivers regarding what is and is not permitted. This provides the context for the restrictions you will apply in the portal. 3. Configure Profiles: Navigate to your fleet portal dashboard. Access the "Card Management" or "Profile Settings" section. Assign specific restrictions to each card. If you have different roles (e.g., field technicians vs. executive management), create distinct profiles for each. 4. Review Exceptions: Periodically check the "Declined Transactions" log in your dashboard. A high volume of declines may indicate that your product code restrictions are too tight, potentially hindering necessary operations, or that a driver is attempting to deviate from company policy.
Common Troubleshooting and Operational Challenges
Even with a well-configured system, issues can arise. The most frequent cause of confusion is the "Declined Transaction" during a time-sensitive delivery or service call.
- Pump Selection Errors: Occasionally, a driver may select the wrong fuel grade on the pump, which uses a different product code than the one allowed on their card. Instruct drivers to be diligent about selecting the grade that matches their assigned profile.
- Station System Downtime: If a station's internal POS system fails to correctly transmit the Level III product code data to the network, the card may be declined as a security precaution. In such cases, the transaction is rejected because the system cannot verify the identity of the purchase, not because the purchase itself is prohibited.
- Outdated Profiles: When a vehicle is replaced or a fuel type is changed, managers sometimes forget to update the product code permissions for the new card. This is a common point of friction. Regularly auditing your asset list against your card restrictions is a recommended best practice.
Frequently Asked Questions
Can I allow fuel purchases but block car washes? Yes. Product codes are granular enough to separate "Fuel" from "Service" or "Merchandise" categories. You can enable fuel codes while keeping "Car Wash" or "Convenience Store" codes set to "Restricted" within your account profile.
What should I do if a driver is declined for a legitimate purchase? First, check your portal’s "Declined Transactions" report to identify the reason. If it was a code restriction, you may need to update the card profile. If it was a communication error at the terminal, advise the driver to try a different pump or a different station.
Are these codes universal across all gas stations? While most major fuel networks use standardized product coding, the way they are categorized can vary slightly. Marathon’s system is designed to interpret these codes accurately across its network of participating locations.
How often should I review my product code settings? It is recommended to review your settings at least twice annually, or whenever there is a significant change in your fleet composition, such as adding new vehicle models or changing maintenance vendors.
Can I set different product code rules for different drivers? Yes. Marathon fleet programs typically allow you to assign specific, unique profiles to individual cards. This means you can have a "Supervisor" card with fewer restrictions and a "General Driver" card with strict fuel-only limitations.
Next Steps for Fleet Managers
If you are currently managing a fleet and are experiencing high administrative overhead regarding receipt reconciliation, the immediate next step is to log into your Marathon fleet account portal and run a "Transaction Detail" report. Identify the frequency of non-fuel purchases. If you notice a pattern of unauthorized spending, use the "Product Restrictions" or "Profile Management" settings to whitelist only the specific fuel or service codes required for your operations. If you are not yet leveraging these tools, consulting your account representative to enable Level III reporting will provide the necessary data visibility to begin implementing these controls. Effective use of product codes transforms your fleet card from a simple payment method into a robust, automated management asset that actively safeguards your company’s bottom line.
Image Gallery
Select an image to open it in a new tab.
Vivian Cho
Executive IT and Emerging Technologies Reporter
