Is it mandatory that service cataloge structure need to be start with service components and other details need to be derived from that.
Or it can also be start with support options and relavent details can be filled in respectively.

For example:- Can service catalog created like
Support option (Via phone support or email support providing in seperate row) -> Region (with respect to support option in each row) -> Service Availability -> SLA and etc...

It's always a good idea to design your service catalogue in a way that will fulfil its purpose, including maintaining its reliability, completeness and usefulness.

I'm curious about why you think things can be mandatory in ITIL (I presume that is what you meant). We often get people asking such questions and I cannot understand where they have acquired such an incongruous misconception._________________"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

Timo, your words will rust in this climate._________________"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718