Aya Teknoloji • ZKONG Authorized Distributor in Türkiye 0541 789 44 27info@ayatech.biz
ServicesAya Teknoloji ServicesSRV-INTEGRATION-DISCOVERY

Integration Discovery Service

Aya Teknoloji professional service

AYA Aya Teknoloji
API Integration
SUP Technical Support

Keşif

Define delivery by project scope, not product quantity

Aya Teknoloji services are scoped by stores, system complexity, data structure, field conditions and expected outcomes. They therefore do not use fixed unit-price or stock logic.

AVAILABLE ON REQUEST

This item is not held in ready stock; current pricing and estimated delivery are confirmed through a quote.

Request a Quote

✓ This is not a physical product. Scope, assumptions, deliverables, schedule and total service fee are confirmed in a proposal after review.

Scope-based proposalDefined deliverablesAya Teknoloji specialists
SERVICE SCOPE
01ProviderAya Teknoloji
02Service typeIntegration Discovery Service
03DeliveryProject-based
04SupportSpecialist team support
AYA TEKNOLOJİ PROFESSIONAL SERVICE

How is Integration Discovery Service delivered?

Make data flow, responsibilities and risk visible before development starts.

Integration discovery analyses fields, update rules, security conditions and dependencies between ERP, POS, e-commerce or file sources and ZKONG Cloud.

  • A scope defined for the requirement
  • Explicit deliverables and assumptions in the proposal
  • Schedule and responsibilities agreed before work starts
Open the scope form →
SCOPE DECISION Project based

The same service name does not mean the same effort.

Stores, users, devices, data sources and customisation change the total effort.

  • Starting point and target outcome
  • Customer and Aya Teknoloji responsibilities
  • Acceptance criteria and change boundary
DEFINE THE SERVICE

What information is needed before a proposal?

Share the variables that affect effort for a reliable price and schedule.

01

Current state

Describe the ZKONG environment, stores, devices and any existing integration.

02

Expected outcome

Define the installation, document, template or training output expected at completion.

03

Constraints

Timeline, site access, security policy, data quality and third-party dependencies affect the proposal.

SERVICE SCOPE

Planned deliverables

Deliverables

  • Source-system and stakeholder meeting
  • Field mapping and sample-data review
  • Recommended data flow and integration approach
  • Scope, dependency, risk and effort summary

Customer inputs

  • Source-system technical owner
  • Sample product and price data
  • Available API or file-format documentation

Standard exclusions

  • Production integration development
  • Data correction in the source system
  • Third-party API or license fees
PRICING FACTORS

How is the service fee calculated?

The fee is quoted as a project total based on work packages, effort, field needs and third-party requirements.

Available on request

This item is not held in ready stock; current pricing and estimated delivery are confirmed through a quote.

Request a Quote
PROPOSAL STRUCTURE

What the proposal will state clearly

01

Scope and explicit exclusions

02

Deliverables and acceptance criteria

03

Customer and Aya Teknoloji responsibilities

04

Schedule, service fee and change process

SERVICE FLOW

From request to acceptance

A service starts with scope approval, not a quantity in a shopping cart.

01

Share the need and current state

02

Clarify scope in a short discovery call

03

Approve the proposal with deliverables, schedule and fee

04

Complete the work against acceptance criteria

BEFORE THE PROPOSAL

Frequently asked questions about professional services

Services follow a different buying flow from product orders.

Why can’t I add this service to the cart?

The fee is not fixed per device or unit. We quote a project total after confirming scope, deliverables, schedule and responsibilities.

Does requesting a proposal cost anything?

There is no charge for the initial review and proposal. If a separate technical discovery is required, we state that before it begins.

How is the service schedule set?

It depends on stores, devices, data readiness, field access, customer approvals and third-party dependencies.

Integration Discovery Service