Advanced Configuration

LedgerPort supports multiple stores under a single account. Each store has its own connections, mappings, and sync settings — data is strictly isolated between stores.

Adding a New Store

1. Go to Settings → Stores and click Add Store.
2. Name the store (e.g., “US Store”, “EU Store”, “Wholesale”).
3. Connect its source and destination platforms.
4. Configure mappings for this specific store.

Entity Separation

If you operate multiple legal entities, each store can sync to a different company file in QuickBooks or a different Xero organization. This keeps financials cleanly separated for tax and reporting purposes.

Shared vs Independent Mappings

• Independent (default): Each store has its own mapping rules. Best when stores sell different products or use different chart of accounts.
• Shared template: Apply the same base mappings to multiple stores, then override per-store where needed. Enable in Settings → Stores → Mapping Templates.

Sync rules let you conditionally route, transform, or skip transactions based on order attributes. Available on Growth and Scale plans.

Rule Conditions

Rules can match on any combination of:

• Order total (e.g., skip orders under $1)
• Product category or tag
• Customer location (country, state)
• Payment method
• Sales channel (online vs POS)

Rule Actions

• Route: Send to a specific account based on conditions (e.g., wholesale orders → Wholesale Revenue).
• Skip: Exclude matching transactions from sync entirely.
• Tag: Add a memo or class to the accounting entry for easier reporting.
• Transform: Modify field values before syncing (e.g., append store name to memo).

Example

{
  "name": "Route wholesale to separate account",
  "conditions": {
    "customer.tags": { "contains": "wholesale" },
    "order.total": { "gte": 500 }
  },
  "action": {
    "type": "route",
    "account": "Wholesale Revenue"
  }
}

Manage rules in Settings → Sync Rules. Rules are evaluated top-to-bottom; the first match wins.

When you first connect LedgerPort or need to backfill past data, you can run a bulk historical sync to import orders from a specific date range.

How It Works

1. Go to Settings → Sync Preferences → Historical Sync.
2. Select the date range you want to import (e.g., last 6 months, last year, or custom).
3. Click Start Historical Sync.
4. LedgerPort processes orders in chronological batches, respecting rate limits on both platforms.

Important Notes

• Historical sync runs alongside live sync — new orders continue to process normally.
• Large imports (10,000+ orders) may take several hours depending on API rate limits.
• Duplicate prevention is active — if any orders were previously synced, they’re skipped.
• Monitor progress in Dashboard → Bulk Operations.

LedgerPort retains full audit logs and sync history for compliance and debugging purposes.

Retention Periods

Exporting Data

Export your data at any time in CSV or JSON format:

• Audit log export: Dashboard → Audit Log → Export. Filter by date range and status.
• Mapping export: Settings → Mappings → Export All. Useful for backup or migrating between accounts.
• API export: Use the GET /audit-log?format=csv endpoint for programmatic exports.

Exported data includes all fields visible in the dashboard: timestamps, order IDs, amounts, statuses, error messages, and full request/response payloads (within retention window).