Dispatch specification
Order sources, parcel data and supported shipping options agreed.
Connect your store or fulfillment system to Sendcloud with an agreed flow for shipment data, labels and tracking. Give dispatch staff a consistent procedure for creating and reviewing parcels.
Start this brief
Order sources, parcel data and supported shipping options agreed.
The required addresses, items and parcel identifiers mapped.
The selected label flow and tracking return connected.
Address errors, repeat requests and status mapping tested.
Actual project screenshots. Some client interfaces are in their original language.

Home services in the United States. Actual project screenshots. Some client interfaces are in their original language.

Ecommerce platform. Actual project screenshots. Some client interfaces are in their original language.

Commercial interior projects. Actual project screenshots. Some client interfaces are in their original language.
We define the scope and prepare the agreed first prototype or work plan before payment.
You approve the prototype and pay 30%. We begin the agreed implementation.
We show the main pages and functions or agreed milestone deliverables. After acceptance, you pay the next 30%.
We finish the agreed checks and hand over the project, materials and access. You pay the remaining 40% after acceptance.
Scope agreed before work begins. All prices in USD. Applicable taxes and third-party fees are confirmed in the proposal.
We agree the scope and prepare the first prototype before the first payment. You can review the proposed structure and customer journey before deciding to proceed.
The agreed initial prototype covers the key page or customer journey. For SEO, advertising and other projects without an interface, the first reviewable result is a proposed work plan. The number of screens and revisions is agreed in the brief.
You approve the prototype or work plan and pay 30% of the agreed project price. We then begin implementation.
We demonstrate the agreed main pages and functions, or the named project deliverables. Once you accept this milestone, the next 30% is due.
We complete the agreed checks, deliver the project and hand over the agreed materials and access. The remaining 40% is paid after acceptance.
This schedule applies to projects with a fixed scope. Monthly work and small hourly tasks have separately agreed terms. Advertising spend, hosting, licences and third-party fees are listed separately in the proposal.
We deliver remotely. Briefing, reviews and handover take place online, with the meeting times and working language agreed in advance.
Scope, selection criteria and practical delivery details.
Your webshop may create the shipment while a warehouse system prepares the parcel. We identify which system starts the process and which system owns each piece of dispatch data.
A supported store connector may cover much of the work. Custom development is scoped around the remaining steps, such as warehouse label requests or returning tracking details to an internal system.
An order reference alone is not a complete integration design. We define the identifiers used to link records and the checks needed before another label request is sent.
Carrier options, address fields, parcel dimensions and service-point choices depend on the agreed setup. Sendcloud and store statuses may differ, so the connection needs a deliberate mapping rather than copying labels between systems.
We check a valid parcel, an invalid address, an unavailable option and a repeated request. Staff should be able to find the label, track the parcel and identify a shipment that needs correction.
Vladimir Nikolaev agrees those checks with you. Carrier charges, account plans, return handling and multi-parcel orders are clarified separately when setting the development scope.

CEO and web development & SEO expert. Web developer and SEO specialist since 2015. Vladimir Nikolaev reviews data rules, implementation choices and acceptance checks with you, so the technical work follows a defined business task.
Answered by Vladimir Nikolaev.
Not always. A supported webshop connector may be sufficient; custom work is assessed against the missing workflow.
No. Shipping charges, account plans and labels are separate from development work.
Yes, where the store supports the required fields. We agree how Sendcloud statuses map to your order states.
Yes, subject to the available provider flow. Their rules and staff actions need a separate place in the specification.

Give your team one place to manage requests, records and approvals. We build browser applications around the work people actually do, with clear access rights and a practical first release.

Add the function your website is missing without rebuilding the whole system. We develop extensions with a defined job, manageable settings and checks against your current platform.

Help buyers estimate a service or configure a product before they contact you. We turn your pricing rules into a clear calculation, with useful explanations and a route to a qualified inquiry.
Send your store or warehouse system, carrier setup and label requirements. We will define the shipment handover and test cases.