An unconstrained template accepts any type and fails deep inside its body when the type does not fit, with a long error. Concepts (C++20) state the requirements up front: template <std::integral T> accepts only integer types, and a call with a double is rejected at the call site with a short message.
The header <concepts> defines many: std::integral, std::floating_point, std::same_as<T, U>, std::convertible_to<From, To>, std::totally_ordered<T>. You write your own with concept and a requires expression that lists what must compile, for example requires(const T& x) { { x.price() } -> std::convertible_to<long long>; }. A type satisfies it if x.price() compiles and returns something convertible to long long.
Use a concept in place of typename, or after the template head with requires. When two overloads both match a call, the more constrained one wins, which lets you write a general version and a special case side by side. The tests here ask the compiler whether a call would compile, with a requires expression of their own.
A concept names the requirement; the template states it in its header.