Setting up your route something like this might work, assuming you controller is named ProductPageController and that you don't use /product/ in other url:s on the site

RouteTable.Routes.MapEnterpriseRoutes(
	 name: "ProductRouting",
	 url: "{language}/{node}/product/{productId}/{page}/{action}",
	 defaults: new { controller = "ProductPage", action = "ShowProduct", searchTerm = UrlParameter.Optional, page = UrlParameter.Optional }
);

And then you can add a ShowProduct method in you controller and retrive the id and load the correct view

public ViewResult ShowProduct(JobPage currentPage, string productId) {

	throw new NotImplementedException("load view for product " + productId);
			
}

Using IPartialRouter should work and it has the benefit of not needing to find a pattern or reserve the phrase "product" in the URL as long as have specific page type for this.

Can you post the code you were trying with?

Johan,

Thanks for the tip - I ended up implementing a custom segment.

I was wondering about IPartial router, but the signature for the interface(IPartialRouter<T1, T2>) didn't seem right - although I hadn't tried it with T! the same type as T2.