English
Advantage Help Center Go to Advantage

Hello. How may we help?

Configure the POS

Configure a Gilbarco Passport POS for Advantage

Confirm Passport's recurring XML exports and collect the register facts Advantage needs for accurate onboarding.

Purpose

Use this guide on the actual Gilbarco Passport Manager Workstation after the store computer can reach the reviewed XMLGateway share. A mapped share on the backoffice computer does not mean Manager Workstation is installed there.

This step turns on the recurring register exports Advantage reads and records the register configuration needed to interpret them correctly. It does not unlock Advantage POS writes.

Step 1: Confirm Third Party Data Interface options

On Passport, select Tools → Manager Workstation → Setup → Store → Third Party Data Interface.

Turn on these six options when that screen is present:

  1. Generate Transaction Level Detail (PJR)
  2. Zip Individual PJR Files at store close
  3. Export Price book when price book is imported from an external source
  4. Export Price book on a nightly basis
  5. Copy inbound item list, combo and match files
  6. Copy end of period XML summary files

Select Save after all six visible options are confirmed. If this Passport release does not expose Third Party Data Interface, do not guess at an equivalent label; ask the store’s Gilbarco ASC which controls apply to that exact version.

Step 2: Review NACS XML 3.4 Back Office Configuration

This is a separate surface from Third Party Data Interface. Open Manager Workstation → Set Up → Store → Back Office → Back Office Configuration, then select NACS XML v3.4.

Confirm the following recurring-feed settings:

  • Generate Transaction Level Detail (PJR) is on.
  • Documents/PJR export is on for the normal recurring feed.
  • Generate Acknowledgement Files is on if this Passport build exposes that control.
  • Use Manifests is off for recurring PJR polling.

Some Passport builds expose no acknowledgement toggle. ACK generation is optional in the NACS XML v3.4 interface, so a missing control is not an onboarding blocker. Photograph the screen, record “ACK control not exposed,” and continue. Do not hunt through unrelated menus or change another transport mode.

“Use Manifests off” applies only to the recurring transaction feed. A FILEMANIFEST created later by an attended one-time Pricebook export is different and must be preserved with every file it lists.

Step 3: Photograph all four tabs

Before selecting Save, take clear photos of the complete Back Office Configuration tabs:

  • Documents
  • Generation Options
  • Polling Options
  • Import Options

Include the full tab, selected NACS version, and Passport software version when visible. Avoid photographing customer payment data or employee credentials. These photos let Advantage review labels that vary by Passport release without asking the store to repeat the visit.

Step 4: Record the register facts

Accurate POS time and store configuration matter as much as the XML checkboxes. Before leaving Manager Workstation:

  1. Confirm the clock is correct for the store’s local time.
  2. Confirm the business date is current. A stale business date can file many days of sales under one date.
  3. Photograph the complete tax table.
  4. Photograph the complete department list, including identifiers and names.

If the clock or business date is wrong, stop and contact the store’s Gilbarco provider. Do not force a day close or edit taxes or departments as part of onboarding.

Verify the result

After Save:

  • Advantage sees fresh PJR files written by Passport on the exact reviewed XMLGateway share.
  • The six Third Party Data Interface options are recorded, or their absence is escalated to the Gilbarco ASC.
  • All four Back Office Configuration tabs are photographed.
  • ACK is either enabled or documented as unavailable and nonblocking.
  • Recurring manifests remain off.
  • Clock, business date, tax table, and department list are recorded.
  • Advantage POS push remains locked until the separate baseline, readback, and canary review is complete.

Seeing XMLGateway or a fresh PJR proves read-side reachability. It does not by itself prove catalog completeness or permission to send changes back to Passport.

Was this article helpful?