OPLOG’s SalesOrder API provides comprehensive order management capabilities for various business scenarios. This guide covers the essential requirements, configurations, and examples for creating different types of sales orders.

Integration Overview

The SalesOrder API is designed to handle multiple business models:
  • E-commerce Integration - Direct website orders with payment processing
  • Marketplace Integration - Orders from platforms like Amazon, Trendyol, etc.
  • B2B Orders - Corporate orders with specialized billing requirements
  • Cross-border Orders - International shipping with currency support
All orders must include unique reference numbers, customer information, and delivery addresses. Optional features like gift services and document attachments enhance the customer experience.

Creating Orders

OPLOG’s SalesOrder POST endpoint has several required fields that you need to be aware of:

Quick Start Requirements

Essential Fields: Reference number, sales channel, customer info, addresses, line items, and payment details are mandatory for all orders.

Core Requirements

Address Requirements

Address requirements vary by location and order type. Both shipping and billing addresses follow the same structure.

Line Items

Each product in the order requires specific information for proper processing.

Payment Options

For COD orders, totalPaymentAmount field is mandatory and must be accurate.
1

Choose Payment Method

Select from Paid, CreditCard, or Cash (COD) based on your business model
2

Set Payment Amount

Ensure totalPaymentAmount matches the order total
3

Specify Currency

Use ISO 4217 currency codes (USD, EUR, TRY, etc.)

Marketplace Integration

Marketplace orders require at least one cargo identification method to be processed successfully.

Cargo Types

Value Added Services (VAS)

Currency Support

Currency information is mandatory for international orders from Turkey. Incorrect currency values are the customer’s responsibility.

Date Format

All date fields use ISO-8601 format as UTC+0.
Example: "2025-06-17T10:13:41.479Z"

Error Handling

Validation Errors

404 Not Found: Mandatory fields missing or invalid values

Business Logic Errors

Blocked Orders: Orders may be blocked due to insufficient stock
Always validate required fields locally before API submission to avoid common errors.

Order Examples


TAG Management

OPLOG.ONE’s TAG management system provides flexible metadata tagging capabilities across various business entities. Organizations can attach custom labels to records, transforming basic data into actionable intelligence for better workflow optimization. The system proves valuable for both operational efficiency and analytics. Teams can quickly identify and process records based on specific criteria - staff can locate items requiring special handling, managers can prioritize high-value transactions, and leadership can analyze performance metrics across different categories. This flexible approach eliminates rigid classification systems, allowing businesses to evolve their tagging strategies as operational needs change.

TAG Best Practices for Sales Orders

Sales Team Assignment

Track sales team members and assignments: sales-team-member, account-manager, lead-source

Order Type

Categorize by type: b2b, retail, wholesale, gift-order

Source Tracking

Track order sources: website, mobile-app, marketplace, phone

Special Handling

Mark special requirements: fragile, expedited, white-glove
TAG Usage Examples:
  • Sales Team Tags: sales-team-member,account-manager,lead-source
  • Source Tags: amazon,trendyol,website,mobile-app
  • Special Tags: gift-wrap,international,b2b,wholesale
  • Processing Tags: reviewed,approved,on-hold,expedited
TAG management for sales orders enables enhanced order tracking, custom workflows, and detailed analytics based on your business requirements.