Booking Providers

How DigiWedge TeeTime integrates with external tee sheet systems.

Overview

DigiWedge TeeTime supports multiple booking provider backends, allowing clubs to:

• Use DigiWedge as the source of truth (INTERNAL)
• Sync with existing club management systems (MCA, Lightspeed)
• Aggregate from third-party booking platforms (GolfNow, ForeUP)

Supported Providers

Provider	Type	Direction	Status
INTERNAL	Native	Read/Write	Production
MCA	Legacy CMS	Read/Write	Production
LIGHTSPEED	Golf POS	Read/Write	Production
GOLFNOW	Marketplace	Read-only	Production
FOREUP	Tee Sheet	Read/Write	Production

Architecture

flowchart TB
    subgraph DigiWedge
        API[TeeTime API]
        Router[Booking Router]
        Map[Provider Map]
    end

    subgraph Providers
        INT[Internal DB]
        MCA[MCA Backend]
        LS[Lightspeed]
        GN[GolfNow]
        FU[ForeUP]
    end

    API --> Router
    Router --> Map
    Map --> INT
    Map --> MCA
    Map --> LS
    Map --> GN
    Map --> FU

Provider Routing

Each booking is associated with a provider via BookingProviderMap:

Field	Description
bookingId	DigiWedge booking reference
provider	Provider enum (INTERNAL, MCA, etc.)
providerBookingRef	External booking ID
externalRef	Customer-facing confirmation
paymentProvider	PSP used for payment
paymentRef	Payment transaction ID

Club Configuration

Clubs configure their tee sheet provider at the course level:

{
  "courseId": "course-uuid",
  "teeSheetProvider": "LIGHTSPEED",
  "providerConfig": {
    "apiKey": "ls_xxx",
    "facilityId": "12345",
    "syncInterval": "5m"
  }
}

Provider Capabilities

INTERNAL

Native DigiWedge tee sheet:

• Full read/write access
• Real-time slot management
• Direct database control
• All features available

MCA (MyClubAccount)

Legacy club management integration:

• Bidirectional sync
• Member data integration
• Pricing from MCA rules
• Handicap sync

LIGHTSPEED

Golf POS and tee sheet:

• Slot availability polling
• Booking push to Lightspeed
• Payment reconciliation
• Member lookup

GOLFNOW

Third-party marketplace:

• Inventory feed (read-only)
• Bookings pulled on schedule
• Rate sync from GolfNow
• No direct booking creation

FOREUP

Cloud tee sheet platform:

• API-based slot sync
• Real-time availability
• Booking creation
• Cancellation sync

Sync Patterns

Real-Time

For providers with webhooks or push APIs:

1. External system sends event
2. DigiWedge receives webhook
3. Internal state updated
4. Players notified if needed

Polling

For providers without push:

1. Scheduled job runs (configurable interval)
2. Fetch changes since last sync
3. Reconcile with internal state
4. Flag conflicts for review

Hybrid

Combination approach:

1. Real-time for critical events (bookings)
2. Polling for bulk data (availability)
3. Conflict detection and resolution

Conflict Resolution

When DigiWedge and provider disagree:

Scenario	Resolution
Double booking	Provider wins, DigiWedge cancels
Price mismatch	Log warning, use provider price
Slot blocked	Provider wins, update internal
Player mismatch	Flag for manual review

Error Handling

Provider failures are handled gracefully:

1. Retry with exponential backoff
2. Circuit breaker after repeated failures
3. Fallback to cached data where safe
4. Alert operations team

Metrics

Track provider health:

• Sync latency
• Error rates
• Conflict frequency
• Availability accuracy

Adding New Providers

Contact DigiWedge to integrate a new booking system. Requirements:

1. API documentation
2. Test environment access
3. OAuth or API key authentication
4. Webhook capability (preferred)

Troubleshooting

Bookings Not Syncing

1. Check provider API credentials
2. Verify network connectivity
3. Review sync job logs
4. Check for rate limiting

Availability Mismatch

1. Compare sync timestamps
2. Check polling interval
3. Review conflict log
4. Force manual sync

Payment Reconciliation

1. Verify paymentRef mapping
2. Check PSP transaction status
3. Review provider confirmation
4. Contact support if unresolved