TRIFECTA CONNECTIONS / SOURCE SYSTEMS
Your records.
Your connected systems.
Your history belongs in your ERP—even before every product, customer or order has a match.
REGULATED INVENTORY
METRC
Bring source records into the ERP with their identifiers and license context. Cultivation and manufacturing licenses belong to the same business, but their inventory needs to stay correctly attributed.
History and everyday changes.
- License-specific integration configuration
- Historic backfill and daily sync workflows
- Inventory, items and harvest context
- Source records independent of Apex product mappings
Available records and endpoints depend on your jurisdiction, license permissions and what METRC makes available. Historical sync can take time and respects API pacing.
FINANCIAL SOURCE RECORDS
QuickBooks
Authorize your own QuickBooks company and bring customers, invoices and payments into the ERP. Financial history should not wait for an optional sales-channel match.
Your company. Your authorization.
- Customer-owned QuickBooks sign-in and consent
- Historical customer and transaction import workflows
- Matching after source records are imported
- Connection and sync status visibility
Account access, source availability and the authorized QuickBooks company determine what can be imported. We review integration fit during onboarding.
OPTIONAL SALES CHANNEL
Apex Trading
Connect Apex when it’s part of your sales workflow. Manage product mappings to connect channel items with operational items.
An integration—not the foundation.
You do not need Apex for a METRC shipment or an invoice to exist. Trifecta ERP includes its own wholesale portal, and source imports stand independently of Apex matching.
Explore wholesale workflows ↗A CONNECTED OPERATION
Use what fits.
Leave out what doesn’t.
Not every cultivator uses METRC. Not every sales team uses Apex. Your setup should reflect your business, not someone else’s stack.
Discuss your systems ↗COMMON QUESTIONS
Do we need an Apex subscription?
No. Apex is an optional integration. The ERP has its own wholesale portal and independent invoice and inventory workflows.
Can we use cultivation and manufacturing licenses?
The ERP supports license-specific cultivation and manufacturing workflows. We’ll review your jurisdiction, source access and license setup with you.
Does historic import mean every record is instantly available?
No. Backfills retrieve the history available through the source system. Volume, API pacing and source permissions affect runtime and coverage. Date ranges alone do not prove a complete import.
What about email, staff invitations and other services?
We’ll confirm the communication services and account configuration needed for your rollout. Tell us which tools your team uses so we can discuss the appropriate connection path.