1C to Ozon integration for a team in Novosibirsk
Exchange products, stock, prices, orders, shipments, returns and reporting with 1C.
Delivery focus: Organize remote delivery with explicit checkpoints.
What we discuss first
products, stock, prices, orders, statuses, identifiers and confirmed API methods.
What we accept in the result
object mapping, test exchange, error log and safe retries.
Boundaries and dependencies
Ozon API rules and availability can change; accounting configuration work is separate.
Integration coordination in Novosibirsk
For an integration project, we confirm system owners, data and failure behavior; city coordination helps agree these decisions with the team in Novosibirsk. Meetings follow Novosibirsk time, UTC+7. Delivery is remote; OTON does not claim an office, employees or local representation in this city.
Brief prompt
What needs a meeting, and what can be reviewed asynchronously?
Hand-off check
Record decisions, questions, versions and the next stage.
Offer geography
Before work starts, we confirm whether the offer is intended for Novosibirsk, Russia or several markets. This affects language, form fields, required information, analytics and campaign settings; no unsupported local promises are added.
Local delivery context
For system-to-system exchange, discovery records data categories, recipients, retention and access controls; the customer confirms the legal basis. Официальный интернет-портал правовой информации.
City context
The city department is responsible for Novosibirsk's telecommunications, digital infrastructure and informatization strategy. Integration discovery records infrastructure and system owners, responsibility boundaries, interfaces and support arrangements. Acceptance requires an agreed ownership map, exchange monitoring, error logs and an escalation runbook. Official website of Novosibirsk.
Question before the brief
Can we start with stock and prices? Yes, as a standalone agreed phase. Can meetings be reduced? Yes, with one agreed written review process.