Skip to main content
This page summarizes the Order → Stock Allocation → Billing → Payment flow in Sanka from a system design and administration perspective. For a business-facing explanation of the process, refer to:

​
Who this page is for

  • IT / information systems teams
  • Owners of Sanka implementation or migration projects
  • Teams planning data migration or integration with existing core systems

​
Core building blocks

Sales operations in Sanka are built around:
  • Master data: Company, Contact, Item, Location
  • Transactions: Order, Inventory Transaction, Invoice, Payment
  • Analytics: Report, Dashboard
Before designing integrations, clarify:
  • Which object is the primary entry point for transactions (for example, Order)
  • How external systems (EC, WMS, accounting, payment services) map to Sanka objects

​
Order: Designing the entry point

  • Decide how order numbers are generated (in Sanka vs. external systems)
  • Define required fields (customer, terms, warehouse, tax settings, etc.)
  • Map IDs from external channels (EC, CRM, etc.)

​
Stock Allocation: Inventory logic

  • Define warehouse-level inventory policies
  • Decide when to allocate stock (at order entry, at shipping instruction, etc.)
  • Handle stock shortages (backorders, substitutes, purchasing)
For operational details, see /en/process/inventory-allocation.

​
Billing / Payment: Receivables design

  • Standardize billing and payment terms (for example, month-end closing rules)
  • Manage invoice numbering and document templates
  • Decide how payment data is registered (manual entry, CSV import, payment service data, etc.)
  • Define matching rules between invoices and payments
Consider accounting integration (CSV export, import into accounting systems) alongside your invoice and payment field design.
For detailed process flows and screenshots, refer to the business-oriented “Sales Operations: Order to Cash” page under the Sales & Commerce section.