Prepare Custom Service Requirements

Prepare Custom Service Requirements

Prepare a Custom Service requirement when the expected result cannot be implemented through standard configuration or the purchased Add-ons.

Custom Service covers requirements that exceed supported Standard behavior, including unsupported data, third-party app, plugin, or module data, bespoke logic, non-standard relationships, schema engineering, external-system handling, and other agreed custom work.

Check standard configuration and Add-ons first

Standard configuration and the four current Standard Add-ons cover defined capabilities. Test supported Standard handling first. Use Custom Service for the portion that remains unsupported, needs a Standard Add-on to be tailored, or requires bespoke Custom Add-on functionality.

Before you prepare a Custom Service requirement

Confirm whether the requirement is covered by one of these paths:

Capability	Use it when	Custom Service threshold
Standard data selection	You need to include supported data types.	The required data is not exposed as a supported data type or supported source record set.
Additional Options	You need supported target-data clearing, name cleanup, description-image handling, identifier preservation, or SEO URL behavior.	The required behavior exceeds the option shown for the migration configuration.
Advanced Attributes Mapping	You need supported Language, Customer Group, or Order Status mapping.	The target value or mapping behavior cannot be represented through the standard mapping control.
Data Filter	You need field-level conditions per data type to control which records migrate.	Required fields, operators, logic, relationships, or external data are unavailable.
Advanced Data Mapping	You need to redirect a supported source field to a different compatible target field without changing the value as part of mapping.	The required field or destination is unsupported, value compatibility cannot be satisfied, or the requirement needs non-standard behavior.
Advanced Database Mapping	You need supported field/database-column mapping and both the Source Platform and Target Platform are Open-Source.	One platform is Non-Open-Source, the field/column or destination is unsupported, value compatibility cannot be satisfied, or bespoke schema behavior is required.
Data Transformation	You need a supported change to the resulting selected target-field value after applicable mapping stages.	The required expression is unavailable, depends on external data, or requires bespoke/multi-record logic outside Standard behavior.

Requirements that usually need Custom Service

• data stored in third-party apps, plugins, modules, or extensions;
• custom fields whose required handling remains outside supported Advanced Data Mapping or Advanced Database Mapping scope;
• database tables or columns that remain unsupported after Advanced Database Mapping eligibility and support are checked;
• tailored or bespoke Add-on behavior that modifies or exceeds a Standard Add-on;
• multi-record or bespoke conditional processing outside supported Data Transformation;
• bespoke relationship reconstruction;
• unsupported filter logic;
• custom platform extraction or target handling;
• data from external systems such as ERP, CRM, marketplace, subscription, or loyalty services;
• target output requiring custom code, custom storage, or non-standard placement.

Prepare the requirement

1. Name the requirement

   Use one clear name for one requirement.

2. Identify the affected data type

   State whether the requirement affects Products, Categories, Customers, Orders, Reviews, Coupons, Pages, or another data area.

3. Identify the source location

   Provide the field name, export column, table, metafield, app area, plugin table, module, API property, or admin location.

4. Describe the target result

   State where the data should appear and what the user should be able to see, search, edit, or validate.

5. Write the logic as a testable rule

   Use an if/then statement where possible. Include fallback behavior.

6. Provide representative examples

   Include at least three normal examples and three edge cases where the data allows it.

7. List dependencies

   Identify required credentials, exports, permissions, apps, plugins, modules, custom fields, or target settings.

8. Define pass conditions

   State which records and fields must match, what differences are acceptable, and what would block sign-off.

9. Submit the requirement in one ticket thread

   Keep examples, files, decisions, and clarification in one traceable support record.

Requirement template

Field	What to provide
Requirement name	Short, unique name.
Affected data type	Data area affected.
Source location	Field, table, export, app, plugin, module, API property, or admin location.
Target destination	Native field, custom field, note, tag, table, reference, or target behavior.
Logic	Testable rule, including conditions and fallback behavior.
Normal examples	Representative source records and expected outputs.
Edge cases	Complex, empty, duplicate, unusual, or risky records.
Dependencies	Access, permissions, exports, integrations, target settings, or applications.
Validation	Samples, pass conditions, acceptable differences, and blockers.

Example requirement

Requirement: Merge an external ERP reference into a project-specific Product relationship
Affected data type: Products
Source location: ERP API data that is not part of the supported migration source
Target destination: Agreed project-specific target relationship
Rule: Match the ERP reference to the migrated Product by the approved identifier and create the agreed target relationship only when the source match is unique.
Validation: Check normal Products, a missing ERP reference, a duplicate ERP reference, and a Product whose source identifier changed.

Assessment, quote, and purchase

Next-Cart assesses the submitted requirement and provides a quote for approved tailored or custom work. If you accept the quote, complete the related Upgrade order for the existing migration.

The upgrade uses top-up pricing. New Value represents the migration’s total value after the approved work is added, and Previously Paid represents the amount already paid. You pay only the additional quoted difference. After payment, the approved work is integrated into the same migration without changing its fixed migration path or extending the original one-year duration.

Expected result

A complete Custom Service requirement should make it possible to determine:

• what data or behavior is required;
• why standard configuration and purchased Add-ons are insufficient;
• where the source data exists;
• what the target result must be;
• which dependencies affect implementation;
• how the result will be validated.

Verify the requirement

Check	Pass condition
Capability boundary	The requirement is not already covered by standard configuration or a purchased Add-on.
Source evidence	Field names, locations, records, screenshots, or exports are provided.
Target expectation	The expected target result is specific and testable.
Examples	Normal and edge-case records are included.
Dependencies	Required access, applications, permissions, and target preparation are listed.
Validation	Pass conditions and blockers are defined.

Failure handling

Issue	What to do
The source location is unknown	Ask the source store owner, developer, or app provider to identify the field, table, export, or API property.
The target destination does not exist	Prepare the required target field or define an approved fallback.
The requirement is too broad	Split it into separate testable requirements.
Examples are unavailable	Collect representative records before requesting implementation.
The requirement may be covered by an Add-on	Compare it with Data Filter, Advanced Data Mapping, Advanced Database Mapping when the path qualifies, and Data Transformation before escalating.
The result cannot be validated	Define concrete sample records and pass conditions before implementation begins.

Next step

Submit the completed requirement through Tickets with source examples, expected target results, dependencies, and acceptance criteria.