Customizing Detail Pages

Using the DashboardDetailFormExtensionDefinition you can customize any existing detail page in the Dashboard.

Use this API when the existing detail page is mostly right and you only need to add data, replace a native field input, or support custom page blocks. You usually do not need to recreate the whole detail route.

Targeting a detail form

Detail form extensions are targeted by pageId. Individual input replacements are also targeted by blockId and field:

Tsx

defineDashboardExtension({    detailForms: [        {            pageId: 'product-detail',            inputs: [                {                    blockId: 'main-form',                    field: 'description',                    component: MarkdownEditor,                },            ],        },    ],});

Use Dev Mode or the Extension Targets reference to find the pageId, blockId, and field name.

Replacing Native Form Inputs

Custom Fields

This feature replaces inputs for native entity fields only, like name, description, slug, or emailAddress.

To customize the form input for a custom field you defined in your plugin, use Custom Field Components instead.

You can replace native detail-page inputs with your own components using the inputs property.

Let's say you want to replace the default HTML description editor with a markdown editor component:

index.tsx

import { defineDashboardExtension } from '@vendure/dashboard';import { MarkdownEditor } from './markdown-editor';defineDashboardExtension({    detailForms: [        {            pageId: 'product-detail',            inputs: [                {                    blockId: 'main-form',                    field: 'description',                    component: MarkdownEditor,                },            ],        },    ],});

To learn how to build reusable input components, see the Customizing Forms guide.

Extending the detail query

You might want to extend the GraphQL query used to fetch the data for the detail page. For example, to include new fields that your plugin has defined so that you can render them in custom page blocks.

index.tsx

import { defineDashboardExtension } from '@vendure/dashboard';defineDashboardExtension({    detailForms: [        {            pageId: 'product-detail',            extendDetailDocument: `                query {                    product(id: $id) {                        relatedProducts {                            id                            name                            featuredAsset {                                id                                preview                            }                        }                    }                }            `,        },    ],});

The extension query must select the same top-level field as the original detail query. For example, the product detail page fetches product(id: $id), so the extension document must also select product(id: $id).

The extra fields become available to page blocks through the page context.entity object:

index.tsx

import { Badge, defineDashboardExtension } from '@vendure/dashboard';defineDashboardExtension({    detailForms: [        {            pageId: 'product-detail',            extendDetailDocument: `                query {                    product(id: $id) {                        relatedProducts {                            id                            name                        }                    }                }            `,        },    ],    pageBlocks: [        {            id: 'related-products',            title: 'Related products',            location: {                pageId: 'product-detail',                column: 'side',                position: {                    blockId: 'facet-values',                    order: 'after',                },            },            component: ({ context }) => {                const relatedProducts = context.entity?.relatedProducts ?? [];                return (                    <div className="flex flex-wrap gap-1">                        {relatedProducts.map(product => (                            <Badge key={product.id} variant="secondary">                                {product.name}                            </Badge>                        ))}                    </div>                );            },        },    ],});

If you are building a custom detail page with useDetailPage(), pass the same pageId to the hook. This allows extendDetailDocument registrations for that page to be applied:

Tsx

const { form, submitHandler, entity } = useDetailPage({    pageId: 'article-detail',    queryDocument: articleDetailDocument,    updateDocument: updateArticleDocument,    createDocument: createArticleDocument,    params: { id: params.id },    setValuesForUpdate: article => ({        id: article?.id ?? '',        title: article?.title ?? '',    }),});

Interacting with the detail page form

Sometimes you want to define a page block that needs to interact with the detail page's form:

To take some action when the form is submitted
To mark the form as dirty from inside your page block

These advanced use-cases can be achieved by using the useFormContext hook from @vendure/dashboard.

Reacting to form submission

Here's how you can use the formState to react to a form submission:

Tsx

import { useEffect } from 'react';import { useFormContext } from '@vendure/dashboard';export function MyPageBlock() {    const {        formState: { isSubmitSuccessful },    } = useFormContext();    useEffect(() => {        if (isSubmitSuccessful) {            console.log('The detail page form was submitted');        }    }, [isSubmitSuccessful]);}

Setting the form as dirty

Let's say you have a page block that interacts with a custom mutation to set some data related to a Product. You want to fire your custom mutation when the form is submitted - this is done using the pattern above.

However, you need to somehow signal to the form that it is now dirty and can be saved, even though no property of the Product itself may have changed.

Here's a pattern to allow this:

Tsx

import { useEffect } from 'react';import { Button, useFormContext } from '@vendure/dashboard';export function MyPageBlock() {    const { register, setValue } = useFormContext();    useEffect(() => {        // We register a "fake" field on the form that we only use        // to track the dirty state of this page block component        register('my-page-block-dirty-tracker');    }, [register]);    return (        <Button            onClick={() => {                // We set that "fake" field to a random value to mark the whole                // form as dirty, so the "save" button becomes enabled.                setValue('my-page-block-dirty-tracker', Math.random(), { shouldDirty: true });            }}        >            Set dirty        </Button>    );}

When to use page blocks instead

Use a page block when the data or UI does not belong inside the generated form grid. Page blocks can access the same context.entity and context.form values, can be placed in the main or side column, and can replace existing blocks when needed.

Use detailForms.inputs only when you want to replace the input for a specific native field. For custom fields, use custom field components.

Was this chapter helpful?

Report Issue

Edited Jun 24, 2026·Edit this page