For a gas station loyalty program ownership change, check the program rights and approved data uses before planning the handoff. Match available points, issued rewards, redeemed discounts, and funding at a dated cutoff. Get a written vendor answer and legal and accounting review, then document access, customer notices, opening records, and open duties in the closing plan.

What should the buyer identify before reviewing balances?

Identify every loyalty program used at the station, including local offers and brand-linked rewards. Ask who operates each program, which legal entity holds the account, and which sites take part. A single app or checkout screen can connect several offers with different rights, funding rules, and records behind them.

Start with the buyer hub and request the agreements, current customer terms, privacy notices, and program reports. List any missing version or approval as an open item rather than infer its terms from a sales presentation. Keep requested changes separate from rights that the vendor and required parties have actually checked.

Use the software contract transfer guide for the wider vendor review. Loyalty needs its own entry because customer rewards, store participation, data use, and settlement can cross more than one agreement. A software login that works today does not prove the buyer may continue every linked feature after closing.

How does a brand program differ from a local program?

Read the terms before assuming the station owns every reward relationship. The Exxon Mobil Rewards+ terms separate the program operator from sponsors and sites that take part. They also set out point limits and sponsor terms. Taking part at a site does not mean owning the program.

That example does not establish the funding or transfer rights in another station’s dealer agreement. Ask the relevant provider to check the site’s status, the new owner, and any approval steps. If the buyer plans to change fuel brand or platform, review the effect on existing offers before promising customers the same experience.

Keep local promotions visible alongside the main program, including offers funded directly by the retailer. Record who sets the terms, who can change them, and who pays when a customer redeems. Do not combine a brand reward, a retailer coupon, and a prepaid service into one liability without examining the separate duties.

Which records belong in the closing register?

Use separate records for legal rights, reward activity, funding, and system access. Each should identify its period, site, reporting source, and named reviewer. That structure makes gaps easier to resolve before the closing team relies on a total or assumes a vendor will complete a requested change.

Loyalty records to match before closing
Review areaRecord to requestQuestion to resolve
Program rightsAgreement and provider written answerMay the proposed owner operate this site?
Customer dataNotices, terms and consent recordsWhich transfers and uses are approved?
Reward statesPoints, issued rewards and event reportsDo the totals overlap or omit held points?
Discount fundingSettlement statements and creditsWho pays and who receives repayment?
Access and supportRoles, integration map and handoff planWho can administer and resolve errors?

Give each open question a named owner and a target date, with the written answer retained. Separate a provider’s general product page from a written answer about the actual account and deal. A claim that the platform supports migration does not approve the specific data transfer, account change, or program continuation.

Why do available points and issued rewards need separate review?

Ask the vendor to explain what each report includes before adding balances together. Square’s Loyalty API overview provides one example: issuing a reward removes the required points from the available balance and holds them in reserve. Redemption removes those reserved points for good, while deleting an unredeemed reward returns them to the account.

That model can show points still available and points held for rewards as separate totals. For example, assume one dated report shows 10,000 available points. A second shows 1,500 points held for issued rewards, which the vendor confirms are outside the first total. The combined 11,500 points show two states in this example, not cash owed or a rule for every vendor.

Keep historical redeemed activity separate from what remains outstanding at the cutoff. Match returns, expired points, manual changes, and pending events using the actual system definitions. Do not delete or expire live balances to make a report match; resolve the cause with the vendor and retain a record of any approved correction.

How should redemption funding be traced?

Trace actual discounts through the POS and the related vendor settlement records. Identify retailer-funded amounts, supported repayments, pending claims, and fees as separate items. A program can create a customer saving without making the whole discount a permanent cost to the retailer or a payment due from the seller.

For a hypothetical period, assume recorded loyalty discounts total $3,200 and documented vendor repayments for those same discounts total $1,800. The difference is $1,400 of retailer-funded discounts before any separate fees or other costs. This example is a period funding review, not a valuation of outstanding points or a forecast of future redemptions.

Check whether the repayment has been received or remains a supported receivable, and identify the date and payee. Match any credit already included in the accounting records before adding it again. Use the POS sales verification guide to trace sales, discounts, returns, and settlement without treating them as the same figure.

What should happen before personal data moves?

Have counsel review the privacy promises, consent records, deal structure, and planned uses. In historical acquisition guidance about Facebook and WhatsApp, FTC staff said privacy promises still matter when a business is sold. Use that source to frame the review of past promises. It does not explain every current state law or rule for marketing consent.

Use summary reports for early diligence where they can answer the question without sharing personal records. Before moving customer-level data, document the approved purpose, access, transfer method, and retention plan with the review team. A contact list can include people with different preferences, and system access does not approve every campaign.

Keep customer notices and marketing plans separate from the internal cutover checklist. Ask counsel and the program provider to review any required notice, consent, or change in terms for the actual deal. Do not send a blanket campaign or promise unchanged rewards while the relevant rights and handoff remain open.

How can the approved handoff be checked?

Build a vendor-approved plan covering site IDs, program settings, account roles, reports, and support contacts. The cybersecurity handoff guide helps coordinate role changes and the removal of prior access. Loyalty review should also check that the buyer can get the needed reports and handle customer reward questions through the approved process.

Use approved test records or the vendor’s approved method to check how points are earned, used, and returned. Check the balance reports as well. Record the expected result, what happened, errors, and who must fix each issue. A working login alone does not test reward rules, funding records, or whether a refund changes the right balance.

Train staff on what to tell customers, who can help, and what staff may change. Write down what happens if a link fails or a customer reports missing rewards during the handoff. Keep each approved fix in the records. Staff should not guess at balance changes or make promises about terms still under review.

What should be matched at the actual cutoff?

Retain dated extracts before and after the agreed handoff, using the same definitions and site scope. Record transactions or vendor events that span the cutoff and explain how they are handled. The accountant and legal team should match any supported duty, receivable, adjustment, or funding mechanism with the final sale documents.

Check who pays a post-close redemption tied to an earlier promise and who collects a later vendor credit. Do not assume the party operating the register receives every payment or bears every old duty. A requested holdback or adjustment needs agreed terms, a supported basis, and a clear release or review process.

Keep signed approvals, opening records, staff instructions, and open items in one file. Compare the opening reports with the approved plan and check differences promptly. Joining a program alone does not prove added profit. Keep the ongoing review tied to supported sales, discounts, costs, and records of customer service.