Match GNet requesters and vehicle types

Goal

Set up the two matching tables 4fleet needs to accept jobs from GNet: which client each GNet requester is, and which of your vehicle classes each GNet vehicle type stands for.

Prerequisites

• You have saved the connection once (see the connection article). The matching tables are refused until a connection exists.
• Your role can edit settings.
• A client exists for every GNet requester you work with, and at least one active vehicle class exists in your catalog.
• Every vehicle class you map has a rate card under Settings > Services & pricing > Rate cards. GNet prices by vehicle class. A mapped class without a rate card makes 4fleet answer GNet that "pricing requires operator review", and the job is not created.

Steps

1. Open Settings > Integrations > GNet Farm In and open the Booking matching section.
2. Under Clients, type the requester's code in GNet requester ID. This is the ID GNet shows for the company that sends you work.
3. In Wholesale client, choose the client that this requester's jobs are booked under. If the list is empty, select Manage clients, add the client, and come back.
4. In Passenger communication owner, choose GNet requester if the requester talks to the passenger, or 4fleet operator if you do.
5. Select Save requester mapping. The message Requester mapping saved confirms it and the pair appears in the list below as the requester ID and the client.
6. Under Vehicle types, choose a GNet vehicle type, for example SEDAN, SUV or VAN_MINI.
7. In 4fleet vehicle class, choose the class you offer for that type. If the list is empty, select Manage vehicle classes and add a class first.
8. Optionally set Maximum passengers. A GNet job with more passengers than this is refused.
9. Select Save vehicle mapping. The message Vehicle mapping saved confirms it. Repeat for every GNet vehicle type you serve and for every requester.

Expected result

Each saved pair shows in the list. A GNet job from a mapped requester with a mapped vehicle type, within the passenger limit, becomes a booking in your account. Jobs from anyone else, or for any other type, are refused and GNet is told why.

Troubleshooting

• If GNet refuses a job with "the requester is not enabled for this integration", add that requester's ID in Clients and save.
• If GNet refuses with "the vehicle type is not mapped for this integration", add the type in Vehicle types and save.
• If GNet refuses with "the passenger count exceeds the mapped vehicle capacity", raise Maximum passengers on that type or map a larger class.
• If GNet refuses with "pricing requires operator review", the mapped class has no rate card. Add one in Rate cards.
• If you save a type again, the new class replaces the old one for that type. It does not add a second mapping.
• If the save fails with The requester mapping could not be saved or The vehicle mapping could not be saved, check that the client is not archived and the class is active.