Amplience Platform Support | US & Canada

Overview

Amplience platform support provides help with maintenance and support requests in an existing implementation. AmpliFabrik works with US and Canadian commerce brands and integrators, including takeovers after support stalls. Scope can cover Amplience CMS (Dynamic Content), schemas, extensions, Dynamic Media, integrations, and publishing workflows. We agree work, access, priorities, and responsibilities. Support can use a bank of hours, with purchase, usage, expiry, reporting, and response terms set in your agreement. Each request has a scope and work record; your team keeps business priorities and release approval. A health check can identify gaps before onboarding. For white-label delivery, the integrator owns the client relationship and controls introductions. AmpliFabrik stays unnamed unless invited, with support through the partner. We are an Amplience Partner Program member, operated by Senior Maple Marketing Ltd. in Saint John, New Brunswick. When requests become a sustained backlog, we can review whether a Managed Retainer would fit the workload.

Schedule a Platform Support Planning Call

Key facts

Amplience CMS controls hub and repository access through user and team roles. When individual and team roles differ, the role granting more access applies. Team access cannot be revoked just by lowering an individual's role.

Source

Registered Amplience CMS extensions have configurable API and sandbox permissions. API access also requires the user to have appropriate permissions. Registering a content field extension lets schemas reuse its name. If the extension is deleted, remove its schema references and synchronize those schemas again.

Source

Amplience CMS webhook activity logs include delivery IDs, requests and responses, and delivery status. Logs are retained for 30 days. Retry behavior depends on the response; failed attempts may need a manual resend.

Source

An Amplience CMS edition contains specific content versions. Editing the content item does not automatically update an edition. Changes can be pushed to unlocked instances; a scheduled edition must be unscheduled first.

Source

How specialist Amplience platform support fits your ongoing maintenance needs

Book a Free Platform Support Consultation

Amplience implementation context helps your team investigate support requests

A support request can cross the content model, editorial tools, media delivery, and storefront code. We review those connections before proposing a change. A publishing issue may need checks of the edition, referenced content, webhook handler, or downstream integration, depending on your implementation. The work record captures the observed behavior, versions, and steps already tried. This gives the person handling the request context and identifies the next steps. Your team can review the proposed scope and dependencies before work proceeds.

Hands typing on a white laptop keyboard with a document open on the screen.

Use an agreed bank of support hours for your team's Amplience needs

An hour bank can fund support requests as they arise. We agree how hours are purchased, approved, recorded, and reviewed, including any minimum, expiry, or renewal terms. Each request is assessed against the support scope and allocation. Reports show the work completed and the balance where a bank is used. This format can suit teams with intermittent Amplience needs. If a backlog develops, we review whether planned capacity through a Managed Retainer would be more suitable.

A couple of monitors sitting next to each other.

Combine current documentation with evidence from your implementation

Support decisions need both platform guidance and evidence from your setup. We use current Amplience documentation, release notes, logs, configuration, and reproductions to investigate a request. The review separates documented behavior from implementation faults and questions that need vendor input. For a publishing issue, that may mean checking content versions, permissions, and integration activity before changing code. Findings record what is confirmed, open questions, and who owns the next step. This preserves the reasoning for future requests.

A man in a gray shirt is using a computer.

Documented handovers preserve context as support roles change

Support can follow delivery by AmpliFabrik or another implementation team. We review the code, content models, integrations, access, and available documentation before agreeing responsibilities. Handover notes identify known issues, release practices, and the decisions behind configuration. If people or roles change, that record helps a new owner understand current work and open risks. Staffing and onboarding are agreed for the engagement.

A close up of a computer screen with code on it.

What an AmpliFabrik Amplience platform support engagement covers

Content type and schema adjustments

We add or refine content types, JSON Schema, validation rules, slots, and content relationships. Before a change, we assess existing content and storefront dependencies. Changes include agreed checks and release steps; data migration or recovery is planned for the affected content.

Common use cases: Content types for campaigns, schema updates after editorial feedback, validation changes, slot patterns, relationship changes, and migration planning when properties or structures change across existing content.

CMS extensions and editorial tool customization

We build or maintain Amplience CMS extensions for fields, content forms, dashboards, and preview tools. Scope includes their configuration, hosting, and permissions. We check changes against content types and editorial tasks.

Common use cases: Field controls, integration panels, preview helpers, locale tools, content validation, and editorial assistance. Where Workforce Flows are included, we plan human review and brand rules around the task, with the required integrations and access agreed.

Dynamic Media template maintenance

We maintain Dynamic Media transformation templates and URL parameters for agreed media requirements. Changes can cover sizing, formats, cropping, and delivery behavior. We check sample assets before publishing changes and identify any account settings that require vendor input.

Common use cases: Image templates for product pages, sizing and format adjustments, point-of-interest cropping, watermark parameters, and delivery URL updates. We agree checks against sample assets and affected storefront components.

Integration maintenance and adjustments

We maintain connections between Amplience, commerce systems, search, automation, and storefront code. Work can include webhook handlers, configuration, error handling, and retry logic. Requests identify affected systems, access, and owners so changes can be checked across the integration before release.

Common use cases: API changes for commercetools or Salesforce Commerce Cloud connections, search update logic, webhook handler errors, automation retries, and content delivery code in Next.js or React. Checks follow the integration behavior and logs, with downstream owners.

Editorial workflow configuration

We adjust authoring, publishing, and access configuration for requirements from your editors. Work can cover editions, scheduling, permissions, and supported workflow features. We identify what is configurable and what needs an extension or integration.

Common use cases: Publishing roles, changes to scheduled editions, locale workflows, review steps, and permissions after team changes. Your content owners define approval and governance requirements; we agree the configuration and checks needed to support them.

Bug investigation and production fixes

We investigate agreed production issues such as publishing problems, integration errors, media delivery changes, and extension faults. Findings inform a fix or vendor escalation, with scope and approval before changes. Emergency response, including its availability and coverage, requires separate agreement.

Common use cases: Edition status checks, scheduled publishing failures, Dynamic Media request errors, extension errors, webhook delivery issues, and integration faults. We record evidence, reproductions, changes, and release checks.

Plan an Amplience Platform Support Engagement

What AmpliFabrik delivers

Support provides an agreed allocation of hours, Amplience expertise for scoped requests, work and usage reporting, and a review of the engagement as needs change. The agreement records terms, response arrangements, approvals, and responsibilities. Your team can see what has been done, what remains open, and how further work is authorized.

01 - An agreed hour bank and support scope

The proposal sets out any starting allocation, rates, payment terms, expiry, renewal, and rules for unused hours. It defines eligible work and request approvals. When the scope or balance needs review, we document the next allocation or change before committing further work to the engagement.

02 - Amplience expertise matched to the work

We identify the engineering, architecture, and coordination roles for the scope. Responsibilities, access, and working overlap are agreed with your team. The work record carries implementation context between requests, with handovers when roles change and vendor questions routed to the owner.

03 - Work and hour usage reports

Reports connect time used with work items, completed changes, open questions, and the remaining balance for hour banks. We agree reporting cadence and detail at the start. Your team can review usage, approve priorities, and decide whether the allocation fits its workload.

04 - Review the move to a Managed Retainer

If support requests become a continuing backlog, we review a Managed Retainer with your team. The decision considers workload, roles, planning, and capacity. Any transition follows agreed commercial, approval, and handover steps. Open work and responsibilities are documented for the next engagement.

Talk to AmpliFabrik About Platform Support

Frequently asked questions

What is Amplience platform support and how does it work?

Platform Support provides help with agreed Amplience maintenance and support requests. We review your setup, scope, access, and priorities, then document the commercial and response terms. Support can use an hour bank, with time recorded against work items. Your team keeps business priorities and release approvals. It can suit an existing implementation with intermittent needs, including a takeover after an integrator exits.

How is Platform Support different from a Managed Retainer?

Platform Support handles agreed requests as they arise and can use a bank of hours. A Managed Retainer provides planned capacity for a continuing backlog of maintenance and development. The fit depends on workload, planning needs, and responsibilities. We agree the charging basis, commitments, and reporting for either format. Any move to a retainer follows a review of workload, terms, roles, and handover needs with your team.

What is the minimum hour bank to start?

Any minimum starting allocation is set in your proposal. We review expected requests, onboarding, and access needs to recommend a bank. The agreement records purchase size, rates, expiry, renewal, unused-hour treatment, and how additional hours are approved.

How does Amplience platform support work alongside other service providers?

We focus on agreed Amplience work and coordinate with owners of your storefront, hosting, commerce systems, and vendor services. Scope can include content types, schemas, extensions, Dynamic Media, publishing, and integrations. We identify owners and dependencies for request routing. Your internal team retains business priorities and release approval. For white-label work, the integrator owns the client relationship and controls introductions. AmpliFabrik remains unnamed unless invited, and ongoing support stays through the partner.

What is the response time for Platform Support requests?

Your agreement sets response arrangements, including hours, channels, priority handling, and escalation. A response commitment is separate from the time needed to investigate or resolve a problem. Timing can depend on access, reproduction, approvals, and vendor input. Emergency Support requires separately confirmed availability and terms; a support request does not establish emergency cover.

Can we engage Platform Support if another team built our implementation?

Yes. We review the implementation, access, documentation, and known issues before agreeing support responsibilities. A health check can help identify gaps and initial priorities. Onboarding records system owners, release practices, dependencies, and open risks. The proposal defines the work needed to establish a usable support baseline.

What does Platform Support cost?

Pricing follows review of your implementation, requests, onboarding, and required expertise. The proposal records rates, any hour-bank terms, included work, and additional charges. Changes to scope, allocation, or coverage follow an agreed approval process. Your team reviews those terms before committing.

How do we know hours are being used efficiently?

Time is recorded against agreed work items, with notes on investigation, changes, and checks. Reports link usage to progress and show any hour-bank balance. We review work that needs more effort or a changed scope with your team before committing additional work. You can use the record to assess priorities, dependencies, and the next allocation.

Amplience platform support for commerce teams in the US and Canada

Overview

Key facts

How specialist Amplience platform support fits your ongoing maintenance needs

Amplience implementation context helps your team investigate support requests

Use an agreed bank of support hours for your team's Amplience needs

Combine current documentation with evidence from your implementation

Documented handovers preserve context as support roles change

What an AmpliFabrik Amplience platform support engagement covers

Content type and schema adjustments

CMS extensions and editorial tool customization

Dynamic Media template maintenance

Integration maintenance and adjustments

Editorial workflow configuration

Bug investigation and production fixes

What AmpliFabrik delivers

01 - An agreed hour bank and support scope

02 - Amplience expertise matched to the work

03 - Work and hour usage reports

04 - Review the move to a Managed Retainer

Frequently asked questions