Pick/MultiValue systems hold decades of business data — customers, orders, inventory, pricing, transactions. The problem isn't the data; it's that modern platforms can't reach it. CRMs want to sync contacts. Accounting software needs invoices. Payment processors send webhooks. E-commerce platforms need real-time inventory. None of them speak Pick natively.
We build the integration layer. REST APIs that expose your Pick data to external systems, and inbound connectors that pull data from the outside world back into Pick. The result: your jBASE, UniVerse, UniData, or D3 system becomes a connected participant in your stack instead of a data silo.
REST API development
We build custom REST endpoints that sit in front of your Pick system. A PHP application handles the HTTP layer — authentication, request parsing, JSON serialization — and calls into Pick for the actual business logic and data access. Your Pick programs stay in Pick BASIC; the API layer handles the protocol translation.
Common endpoints we've built: order lookup, inventory availability checks, customer account status, pricing queries, shipment tracking, and transaction history. Each returns clean JSON that any modern application can consume.
HubSpot integration
We've built bi-directional data syncs between Pick systems and HubSpot. Contacts, companies, deals, and custom properties — flowing both directions, staying in sync. When sales updates a contact in HubSpot, the change propagates to Pick. When an order ships in Pick, the deal stage updates in HubSpot.
The hard part isn't the HubSpot API — it's the bi-directional sync logic: conflict resolution when both sides edit the same record, avoiding infinite sync loops, handling HubSpot's rate limits and batching requirements, and mapping Pick's multivalued data structures to HubSpot's flat property model. We've solved all of these in production.
Salesforce integration
Similar patterns to HubSpot but with Salesforce's OAuth/JWT authentication, its own API conventions, and its own data model quirks. We connect Pick systems to Salesforce for contact sync, opportunity management, and custom object data exchange. If your sales team lives in Salesforce and your operations team lives in Pick, we make them see the same data.
QuickBooks integration
Pick systems often run their own AR, AP, and general ledger — but the accountants want QuickBooks. We build integrations that sync invoices, payments, customers, and chart-of-accounts data between Pick and QuickBooks Online. Automated nightly syncs, real-time pushes on invoice creation, or batch reconciliation — whatever fits your workflow.
Microsoft Power BI integration
Pick/MultiValue systems sit on decades of transactional data — sales history, inventory movements, production metrics, customer activity — but getting that data into Power BI for visualization and reporting has always been a challenge. We build the data pipeline: automated extracts from Pick into SQL databases or direct REST API connections that Power BI can consume natively.
The result: live dashboards and reports in Power BI that pull from your Pick system without manual exports, CSV wrangling, or stale spreadsheets. Sales trends, inventory levels, production throughput, AR aging — whatever your team needs to see, refreshed on a schedule or in real time.
Odoo integration
Odoo is a full-suite open-source ERP and CRM platform, and some organizations run it alongside their Pick system — Odoo for front-office operations and Pick for core business logic. We build the integration layer between them: syncing customers, orders, inventory, and product data bi-directionally so both systems stay current without manual data entry or CSV imports.
Payment processing & webhooks
Modern payment processors — Stripe, Authorize.net, Square, PayPal — communicate through webhooks: HTTP callbacks that notify your system when a payment succeeds, fails, or gets disputed. We build webhook receivers that catch these events and route them into your Pick system, updating order status, posting payments to AR, and triggering downstream processes automatically.
We also build outbound payment flows: your Pick billing system initiates a charge through the processor's API, handles the response, and records the result — all without manual intervention or copy-pasting between systems.
EDI processing
EDI is still the backbone of B2B commerce in manufacturing and distribution. We build and maintain EDI integrations for Pick systems — 810 invoices, 850 purchase orders, 856 advance ship notices, and other standard transaction sets. Inbound parsing, outbound generation, and the mapping logic that translates between EDI's fixed formats and Pick's multivalued data structures.
E-commerce & web platform integration
Inventory counts, product data, pricing, and order flow between your Pick system and web platforms — Shopify, WooCommerce, BigCommerce, or custom-built storefronts. Real-time inventory availability so your website never oversells. Order import so web orders flow into the same fulfillment pipeline as everything else.
Database sync & replication
Pick systems often need to keep data in sync across multiple files or tables — sales transactions flowing into sales analysis, order details rolling up into customer summaries, inventory movements updating warehouse totals. We build automated sync processes that keep these related data stores consistent without manual intervention.
The same pattern extends beyond Pick. When you need Pick data mirrored in a SQL database for reporting, or external data pulled into Pick on a schedule, we build the sync pipeline: change detection, conflict handling, error logging, and retry logic. Real-time triggers for high-priority data, scheduled batch jobs for everything else. Your sales team sees today's numbers in the analysis tables, not yesterday's.
AI service integration
AI APIs — OpenAI, Anthropic, Google — are just another external service your Pick system can call. We build the integration layer: Pick exports the data, PHP calls the AI API, the result comes back into Pick. Product description generation, demand forecasting, document extraction, anomaly detection. See our AI Implementation page for the full picture.
How it works
Our integration approach is practical, not architectural. We use PHP as the bridge layer — command-line scripts and lightweight web endpoints that handle the HTTP, JSON, authentication, and error handling, while Pick stays in charge of the business logic and data. No middleware platforms, no message buses, no infrastructure you need to maintain separately. Just PHP, your Pick system, and the external API.
For high-volume or time-sensitive integrations, we add scheduling (cron-based sync jobs), queuing (file-based job queues), and logging (so you can see exactly what synced, when, and what failed). For real-time integrations like payment webhooks, the response path is immediate — webhook arrives, PHP catches it, Pick processes it, done.
Platforms
We build API integrations on jBASE, Rocket UniVerse, Rocket UniData, Rocket D3, and mvBASE. The integration patterns are similar across platforms; the Pick-side implementation details vary. We've shipped on all of them.