Design stage: there is no released app yet. This site separates what exists in the repository from what is planned. See status
Simca
EspañolRequest access

Launcher, packaging and logistics

Integrations

What Simca is planned to connect with: Interchange, Logistics, accountants, tax portals, online stores, delivery apps an

Status labels: Built in the repository (checked files or developer tooling, not an app feature) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made

What is the plan for “CONN Interchange”, thinking about name undecided?

Planned C0146

The catalog's module for digital waybilling and a supply network between distributors, drivers and stores. The base-layer product name is not decided. Plan for: name undecided; offline handshake; signed files. In the catalog it is a plan and nothing is built.

Open this answer on its own page

Which edge cases come up around “Simca Logistics overlay”, especially around reputation math not decided?

Planned C0147

An overlay on Interchange for job posting, bidding, dispatch and reputation, delivered as an element in a free-pricing-class package. Its board relay needs online sign-in; the peer-to-peer baseline does not. All designs; nothing built. Plan for: reputation math not decided; gps only opt-in; disputes. In the catalog it is a plan and nothing is built.

Open this answer on its own page

How does Simca approach “SUNAT electronic waybill”, thinking about rule changes?

Planned C0148

Peru's electronic transport document (GRE). The catalog plans it as updatable rules data. Plan for: rule changes; offline issuance; driver documents. In the catalog it is a plan and nothing is built.

Open this answer on its own page

Is “Accountant export” supported today, thinking about format expectations?

Planned C0149

Files for an external accountant: sales, purchases, payroll-adjacent and tax books. Plan for: format expectations; period close; corrections after export. In the catalog it is a plan and nothing is built.

Open this answer on its own page

What goes wrong with “CSV import and export” in a shop, thinking about encoding?

Planned C0150

Spreadsheet files are the universal bridge for catalogs, customers and reports. Plan for: encoding; column mapping; duplicates. In the catalog it is a plan and nothing is built.

Open this answer on its own page

Why does “Online store hooks” matter for a small business, thinking about overselling?

Planned C0151

Optional, local-first hooks for an online store, such as order import and stock export. Plan for: overselling; prices that differ online; order status. In the catalog it is a plan and nothing is built.

Open this answer on its own page

What should owners check about “Delivery apps”, thinking about menu differences?

Planned C0152

Orders from third-party delivery services entered manually or by import. Plan for: menu differences; commission accounting; order cancellations. In the catalog it is a plan and nothing is built.

Open this answer on its own page

Is “Payment providers” supported today, thinking about sdk availability?

Planned C0153

Provider SDKs for Tap to Pay. Simca is not a provider and holds no card numbers. Plan for: sdk availability; settlement timing; disputes. In the catalog it is a plan and nothing is built.

Open this answer on its own page

How does Simca approach “Printer and scanner drivers”, in particular regarding vendor quirks?

Planned C0154

Generating printer bytes in the core and reading scanners as keyboards. Plan for: vendor quirks; bluetooth pairing; driver updates. In the catalog it is a plan and nothing is built.

Open this answer on its own page

How does Simca approach “Local API”, in particular regarding authentication?

Not decided C0155

A local API for add-ons, kept optional. Whether and how is not decided. Plan for: authentication; versioning; offline operation. It is not decided.

Open this answer on its own page

Is “Marketplaces” supported today, with a focus on api terms?

Gap C0156

Listing and order sync with marketplaces is not in the catalog beyond CSV. Plan for: api terms; stock sync; fees. It is a gap: the catalog does not cover it.

Open this answer on its own page

What should owners check about “ERP and enterprise systems”, in particular regarding mapping charts of accounts?

Gap C0157

Large organisations may want data passed to their ERP. The catalog provides exports, not live connectors. Plan for: mapping charts of accounts; timing; consolidation. It is a gap: the catalog does not cover it.

Open this answer on its own page

How does Simca approach “Payroll providers”, thinking about statutory rules?

Planned C0158

The catalog lists payroll-adjacent exports for accountants, not a payroll engine. Plan for: statutory rules; tips; time-clock data. In the catalog it is a plan and nothing is built.

Open this answer on its own page

Is “Tax authority portals” supported today, with a focus on provider outages?

Planned C0159

Electronic documents often go through authority portals or accredited providers. Planned for Peru only. Plan for: provider outages; rejected documents; retries offline. In the catalog it is a plan and nothing is built.

Open this answer on its own page

Why does “Barcode and product databases” matter for a small business, considering data quality?

Gap C0160

Importing product names from shared databases. Not in the catalog. Plan for: data quality; licensing; local products missing. It is a gap: the catalog does not cover it.

Open this answer on its own page

What should owners check about “Messaging and notifications”, especially around customer consent?

Planned C0161

Sending receipts or statements by messaging apps. Optional and provider-dependent. Plan for: customer consent; delivery failure; privacy. In the catalog it is a plan and nothing is built.

Open this answer on its own page

How does Simca approach “Maps and routing”, in particular regarding offline maps?

Planned C0162

Navigation and ETA for drivers, offline where possible. Plan for: offline maps; geofencing opt-in only; battery use. In the catalog it is a plan and nothing is built.

Open this answer on its own page

Which edge cases come up around “Scales and device protocols”, especially around protocol variety?

Planned C0163

Reading weight from counter scales. Plan for: protocol variety; stability; legal-for-trade. In the catalog it is a plan and nothing is built.

Open this answer on its own page