Shopify
LiveAdmin GraphQL reads for orders, products, customers, inventory signals, and fulfillment context.
oproom starts with the systems e-commerce founders already operate: commerce, inventory, support, marketplaces, fulfillment, ads, analytics, payments, and mailbox context. The wall below keeps the roadmap honest without turning the product into a generic connector hub.
Read surfaces are available for investigation and brief generation. Shiprocket is the next fulfillment connector because shipping, returns, and RTO are core operating problems for this buyer.
Admin GraphQL reads for orders, products, customers, inventory signals, and fulfillment context.

Stock, items, contacts, purchase orders, sales orders, invoices, and inventory movements.
Tickets, contacts, departments, and support pressure that should change an ops decision.
Marketplace and FBA exposure, orders, inventory summaries, and seller account context.
Shipping, courier allocation, tracking, returns, delivery exceptions, and RTO pressure for India-first stores.
Store traffic, conversion context, and SKU pressure from acquisition or landing-page changes.
Campaign spend, performance drift, and demand spikes that can create fulfillment risk.
Ad account and campaign reads for promotion pressure, spend drift, and SKU demand signals.
These expand the operating room around the store: finance, customer records, team handoffs, and office systems. Razorpay stays visible here for India-first payment operations.
India payments, refunds, captures, disputes, settlements, subscriptions, and payment links via Razorpay MCP OAuth.
Accounting context for invoices, expenses, cash position, customers, vendors, and reports.
Payments, invoices, subscriptions, disputes, shipment tracking, and merchant reporting.
CRM records, deals, tickets, tasks, meetings, notes, marketing content, and customer history.
Team channels, decisions, escalations, internal handoffs, and operational context.
Outlook, OneDrive, SharePoint, Teams, files, email, calendar, and collaboration context.
Google lists Workspace small-business tools across mail, Drive, Calendar, Chat, Meet, docs, spreadsheets, forms, notes, sites, admin, and no-code apps. Ops Room should expose each one as a connector with an honest status instead of burying it in a roadmap.
Mailbox search and message context for vendor, customer, and internal ops threads.
Appointments, deadlines, supplier calls, campaign dates, and owner availability.
Shared files, supplier decks, operations docs, contracts, photos, and exports.
Vendor notes, SOPs, policies, meeting notes, and generated operating drafts.
Manual trackers, SKU maps, vendor quote sheets, reconciliations, and planning files.
Vendor decks, wholesale presentations, launch recaps, and review material.
Team threads, owner decisions, vendor escalations, and channel context.
Meeting artifacts and calendar-linked context for vendor or team calls.
Owner to-dos and follow-ups created from issues, emails, calls, and watch findings.
Lightweight notes and checklists that often hold founder-only context.
Supplier intake forms, customer feedback, wholesale requests, and internal checklists.
Internal wikis, vendor portals, and lightweight knowledge pages.
Workspace users, groups, aliases, and domain-level account context.
No-code apps and automations already built on top of business data.
Workspace AI artifacts and generated work products that may become useful context.
Some marketplaces and 3PLs start with exports, not clean APIs. oproom can still map recurring reports into the operating brief, then graduate the connector when the workflow proves important.
CSV/report ingestion for regional marketplaces, 3PL exports, payout files, and custom channel data.