Integrations

Go to Integrations > General to review provider availability, connection health, and the next action PeakPOS currently supports for your organization.

Access and scope

The page is organization-scoped. It appears only when you have both:

• org.read
• org.integrations.read

Linked actions can have narrower gates:

• QuickBooks opens for users who can access General, but connecting, reconnecting, disconnecting, changing mappings or modules, syncing, and retrying failures require both org.write and org.admin. Other users see the QuickBooks page read-only.
• Uber Eats uses a store-scoped connection page. Connecting or reconnecting requires a selected store, provider readiness, and both org.write and org.admin; disconnecting requires both organization permissions.
• Scan Data diagnostics require a selected store and store.mkonnekt.read; without that permission, the card shows Diagnostics unavailable.

If General is missing, ask an organization administrator to verify both organization permissions. If the page opens but a linked action is unavailable, read the explanation on that provider card before requesting broader access.

Understand provider status

Each card separates availability from connection health.

Availability

• Live: PeakPOS has a merchant-facing provider workflow.
• Support managed: Peak Support configures the integration; the portal may provide diagnostics.
• Coming soon: The provider is listed for evaluation, but setup is not available yet.
• Deferred: Connection and setup are unavailable in this catalog.
• Not self-service: The related workflow may exist, but this portal cannot configure the provider.

Connection health

Live merchant-managed integrations can show:

• Connected: the provider connection is active.
• Not connected: no active connection is available.
• Pending: connection setup has not completed.
• Needs attention: the provider connection failed or reported an error.
• Disabled: the saved integration is inactive.
• Sync needs attention: the connection is still connected, but one or more sync operations need review.

The card also shows Last sync when a live provider has a recorded sync time. Other cards show Readiness instead.

Providers shown on General

The current page contains only these providers:

Provider	Current portal behavior	Supported next action
QuickBooks	Live; connection and sync health are shown	Manage QuickBooks opens the connection and sync page; changes require both org.write and org.admin
Scan Data	Support managed; diagnostics and the partner SkanData weekly feed are configured by Support	View diagnostics opens selected-store diagnostics when you have store.mkonnekt.read; contact Support for feed setup
Uber Eats	Connection health and store mappings are shown	Use the enabled Connect Uber Eats or Reconnect Uber Eats action to open the store-scoped connection page
Xero	Coming soon	Setup request is not yet enabled; contact Support if you want to evaluate it
FreshBooks	Coming soon	Setup request is not yet enabled; contact Support if you want to evaluate it
DoorDash	Deferred in the integration catalog	Connection and setup actions are disabled in the catalog
HubSpot	Coming soon	Setup request is not yet enabled; contact Support if you want to evaluate it
Gusto	Not self-service	Contact Support; payroll setup is not self-service in the portal

Do not use accounting instructions for delivery, payroll, CRM, or Scan Data providers. Their supported next actions differ.

Check an integration

1. Confirm the organization in the sidebar.
2. Go to Integrations > General.
3. Find the provider under Accounting, Payroll, Delivery, Loyalty & CRM, or Scan Data.
4. Read the status information and connection health shown on the card.
5. Review Last sync or Readiness.
6. Follow only the enabled action on the card.

The count at the top reports merchant-managed integrations currently eligible for sync. Support-managed and non-self-service providers are not included in that count.

Respond to QuickBooks health

• If QuickBooks is Connected and has no attention badge, use Manage QuickBooks to review its supported sync areas.
• If it is Not connected, Pending, Disabled, or Needs attention, select Manage QuickBooks and review the connection state shown there.
• If it says Sync needs attention, review the safe status details on the QuickBooks page. Users with both org.write and org.admin can retry failed work there.
• Connecting, reconnecting, disconnecting, changing sync settings, and retrying require both org.write and org.admin. If you have read-only access, ask an organization administrator with both permissions to perform the supported action.
• If the supported reconnect or retry does not recover the integration, contact Support. PeakPOS withholds provider error details that could expose credentials.

Do not send your QuickBooks password, authorization code, access token, or other credentials to Support.

Use Scan Data diagnostics

Scan Data tobacco discount lookup, diagnostics, and weekly reporting are configured with Peak Support.

1. Select the store whose Scan Data behavior you want to inspect.
2. Go to Integrations > General.
3. On Scan Data, select View diagnostics.
4. If the action says Diagnostics unavailable, ask an administrator to verify store.mkonnekt.read for the selected store.
5. Contact Support for setup or configuration changes.

SkanData weekly order feed

Support-managed mKonnekt integrations can retrieve a weekly order feed from:

• Method and path: POST /api/v1/mkonnekt/skandata

• Authentication: send the configured partner secret in the X-MKONNECT-SECRET header. Missing or invalid secrets return 401 Unauthorized. Never put the secret in the URL or request body.

• Content type: application/json

• Request body:

  {
    "RCN": "123456",
    "weekStartDate": "2026-06-01",
    "weekEndDate": "2026-06-07"
  }

  Dates are ISO calendar dates and the range is inclusive. The start date must not be after the end date, and a request cannot cover more than seven inclusive days. Invalid ranges return 400 Bad Request.

• RCN resolution: the RCN must identify exactly one enabled store configuration. An unknown RCN returns 404 Not Found; duplicate enabled configurations return 409 Conflict until Support corrects the configuration.

• Successful response: the endpoint returns a JSON object with a results array. An empty date window returns "results": [].

  {
    "results": [
      {
        "orderId": "order-example",
        "RCN": "123456",
        "loyaltyId": null,
        "orderTotal": 12.50,
        "items": [
          {
            "bookingTime": "2026-06-03T14:30:00-04:00",
            "product": {
              "upc": "000000000000",
              "name": "Example product",
              "id": "product-example"
            },
            "quantity": 1,
            "description": "Example product",
            "total": {
              "discount": 0.00,
              "base": 12.50
            }
          }
        ]
      }
    ]
  }

  bookingTime is rendered with the configured store's UTC offset. The requested window starts at local midnight on weekStartDate and ends immediately before local midnight on the day after weekEndDate; daylight-saving transitions use the store timezone's actual offsets.

Coordinate feed credentials, RCN setup, and delivery scheduling with Peak Support. Do not include the partner secret or other credentials in support requests.

Delivery providers

For Uber Eats, follow the enabled Connect Uber Eats or Reconnect Uber Eats action to the store-scoped connection page. Choose the affected store and follow the page's enabled action. If the page reports missing configuration, contact Support before attempting to connect. Connection changes require the permissions described above.

DoorDash connection and setup actions are disabled in the catalog. Catalog availability is separate from the health of any historical connection.

What to send Support

If a supported connection remains unhealthy, email support@peakpos.co with:

• Organization and affected store, if store-specific
• Provider name
• Status information and connection health shown
• Last sync time, if shown
• The action you tried and the exact on-screen message
• Approximate time the problem occurred

Never include passwords, one-time codes, API keys, tokens, private certificates, or screenshots that expose those values.